method and apparatus for indicating the frequency location of ss / pbch blocks

专利摘要:
This disclosure refers to a communication method and system to converge a 5th generation (5G) communication system to support higher data rates in addition to a 4th generation (4G) system with Internet of Things technology ( IoT). This disclosure can be applied to smart services based on 5G communication technology and IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, healthcare, digital education, smart retail, security and security services.A UE in a wireless communication system is provided. The UE comprises a transceiver configured to receive, from a BS, an SS / PBCH block including the PBCH using a first frequency location (GSCN-Current) over downlink channels, the GSCN-Current being based on a set of frequency scans. predefined synchronization that is determined by a global synchronization channel number (GSCN). The UE further comprises a processor operationally connected to the transceiver, the processor configured to determine the SS / PBCH block, identify the contents of a PBCH included in the determined SS / PBCH block, determine a configuration for at least one of the SS / PBCH blocks that is associated with a PDCCH including scheduling information for RMSI in GSCN-Current or the SS / PBCH block that is not associated with PDCCH including scheduling information for RMSI in GSCN-Current.
公开号:BR112020012590A2
申请号:R112020012590-3
申请日:2018-12-21
公开日:2020-11-24
发明作者:Hongbo Si；YoungHan NAM
申请人:Samsung Electronics Co., Ltd.；
IPC主号:

专利说明:

[001] [001] The present application generally refers to the signal indication. More specifically, the present disclosure relates to the indication of SS / PBCH block frequency location in an advanced wireless communication system. Prior Art
[002] [002] To meet the demand for increased wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called 'Beyond the 4G Network' or 'Post-LTE System'. The 5G communication system is considered to be implemented in higher frequency bands (mmWave), for example, 60 GHz bands, to achieve higher data rates. To decrease the loss of propagation of radio waves and increase the transmission distance, massive beam-forming, multi-input and multi-output (MIMO) techniques, Full Dimension MIMO (FD-MIMO), array antenna, an analog beam formation, large-scale antenna techniques are discussed in 5G communication systems. In addition, in 5G communication systems, development to improve the system network is underway based on small advanced cells, radio access networks (RANs) in the cloud, ultra-dense networks, device-to-device (D2D) communication, backhaul wireless, mobile network, cooperative communication, Coordinated Multipoint (CoMP), cancellation of interference at the receiving end and the like. In the 5G system, Modulation
[003] [003] The Internet, which is a human-centered connectivity network where human beings generate and consume information, is now evolving into the Internet of Things (IoT), where distributed entities, like things, exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of IoT technology and Big Data processing technology (Big Data) through connection to a cloud server, has emerged. According to technological elements, such as "detection technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology" were required for the implementation of IoT, a sensor network , Machine-to-Machine (M2M) communication, Machine-Type Communication (MTC), and so on have recently been researched. Such an IoT environment can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated between connected items. IoT can be applied to a variety of fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart power grids, healthcare, smart appliances and advanced medical services through the convergence and combination of Information Technology Existing information (IT) and various industrial applications.
[004] [004] Accordingly, several attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as a sensor network, Machine Type Communication (MTC), and machine-to-machine communication (M2M) can be implemented by beam-forming antennas, MIMO, and array antennas. The application of a Radio Access Network (RAN) in the cloud as the Big Data processing technology described above can also be considered an example of convergence between 5G technology and IoT technology.
[005] [005] For a licensed new radio (NR) spectrum, each physical transmission and synchronization channel (PBCH) signal block (SS / PBCH) block comprises a symbol for the primary NR sync signal (NR-PSS), two symbols for NR-PBCH, and one symbol for the secondary sync signal NR (NR-SSS) and NR-PBCH, where the four symbols are mapped consecutively and multiplexed by time division. An NR-SS is a unified design, including the NR-PSS and NR-SSS sequence design, for all carrier frequency ranges supported on the NR. The transmission bandwidth of NR-PSS and NR-SSS is less than the transmission bandwidth of the entire SS / PBCH block. For the initial selection of cells for an NR cell, a UE assumes the standard burst SS set periodicity as 20 ms, and to detect a non-independent NR cell, the network provides burst SS set periodicity information per carrier frequency for the UE and information to derive measurement time / duration. In addition to a master information block (MIB), the minimum remaining system information (RMSI) is carried over the physical downlink shared channel (PDSCH) with scheduling information carried over the corresponding physical downlink control channel (PDCCH). A set of control features (CORESET) to receive common control channels needs to be configured, and can be transmitted on the PBCH. Disclosure of the Invention Technical problem
[006] [006] The modalities of this disclosure provide an indication of SS / PBCH block frequency location in an advanced wireless communication system. Solution to the Problem
[007] [007] In one embodiment, a base station (BS) is provided in a wireless communication system. The BS comprises a processor configured to generate a synchronization signal and physical broadcast channel block (SS / PBCH), identify a first frequency location (GSCN-Current) based on a set of predefined synchronization scans that is determined by a global synchronization channel number (GSCN) to transmit the SS / PBCH block, determine, based on the GSCN-Current, a configuration for at least one of the SS / PBCH blocks that are associated with a downlink control channel (PDCCH) including scheduling information for the minimum remaining system information (RMSI) in the GSCN-Current or SS / PBCH block that is not associated with the PDCCH including scheduling information for the RMSI in the GSCN-Current, determine when the block SS / PBCH is not associated with PDCCH including scheduling information for ISMS in
[008] [008] In another embodiment, user equipment (UE) in a wireless communication system is provided. The UE comprises a transceiver configured to receive, from a base station (BS), a synchronization signal and physical broadcast channel block (SS / PBCH) including the PBCH using a first frequency location (GSCN-Current) over downlink channels, GSCN-Current being based on a set of predefined synchronization scans that is determined by a global synchronization channel number (GSCN). The UE further comprises a processor operationally connected to the transceiver, the processor configured to decode a PBCH included in the SS / PBCH block, identify the contents of the decoded PBCH, determine a configuration for at least one of the blocks
[009] [009] In yet another modality, a method of user equipment (UE) in a wireless communication system is provided. The method comprises receiving, from a base station (BS), a synchronization signal and physical broadcast channel block (SS / PBCH) including the PBCH using a first frequency location (GSCN-Current) on downlink channels , GSCN-Current being based on a set of predefined synchronization scans, determined by a global synchronization channel number (GSCN), decoding a PBCH included in the received SS / PBCH block, identifying the contents of the decoded PBCH, determining a configuration for at least one of the SS / PBCH blocks that are associated with a physical downlink control channel (PDCCH) including scheduling information for the minimum remaining system information (RMSI) in the GSCN-Current, or the SS / PBCH block that is not associated with the PDCCH including the scheduling information for the RMSI in the GSCN-Current, and determining, when the SS / PBCH block is not associated with the PDCCH including the scheduling information for the R MSI in GSCN-Current, the configuration to include at least one of a frequency range in which no other SS / PBCH blocks configured with the PDCCH including scheduling information for the ISMS are transmitted, the frequency range determined based on the GSCN , or a second frequency location in which other SS / PBCH blocks configured with the PDCCH including scheduling information for the RMSI are transmitted, the GSCN-Current determined based on the GSCN.
[0010] [0010] Other technical characteristics can be readily apparent to a person skilled in the art from the following figures, descriptions and claims.
[0011] [0011] Before carrying out the DETAILED DESCRIPTION below, it may be advantageous to define definitions of certain words and phrases used throughout this patent document. The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether these elements are in physical contact or not. The terms "transmit", "receive", and "communicate", as well as their derivatives, cover both direct and indirect communication. The terms "includes" and "comprises", as well as their derivatives, mean inclusion without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with", as well as its derivatives, means to include, be included, interconnect, contain, be contained, connect to or with, couple with or with, be communicable with, cooperate with, intercalate, juxtapose, be close to, linked to or with, have, have a property of, have a relationship with or with or something similar. The term "controller" means any device, system or part of it that controls at least one operation. Such a controller can be implemented in hardware or in a combination of hardware and software and / or firmware. The functionality associated with any specific controller can be centralized or distributed, either locally or remotely. The phrase "at least one of", when used with a list of items, means that different combinations of one or more of the items listed can be used, and only one item on the list may be needed. For example, "at least one of: A, B and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.
[0012] [0012] In addition, several functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer-readable program code and incorporated into a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or a portion of them adapted for implementation in code suitable computer-readable program. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium capable of being accessed by a computer, such as read-only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A "non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that carry electrical or other transient signals. A non-transitory computer-readable medium includes medium where data can be stored permanently and medium in which data can be stored and subsequently replaced, such as a rewritable optical disc or an erasable memory device.
[0013] [0013] Definitions for other specific words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most, such definitions apply to earlier as well as future uses of such defined words and phrases. Advantageous effects of the invention
[0014] [0014] The modalities of this disclosure provide an indication of the SS / PBCH block frequency location in an advanced wireless communication system. Brief description of the drawings
[0015] [0015] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which equal reference numbers represent equal parts: FIGURE 1 illustrates an example of a network without wire in accordance with the modalities of this disclosure;
[0016] [0016] FIGURES 1 through FIGURE 12, discussed below, and the various modalities used to describe the principles of the present disclosure in this patent document are for illustrative purposes only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of this disclosure can be implemented in any properly arranged system or device.
[0017] [0017] The following documents and standard descriptions are hereby incorporated by reference to the present disclosure as if fully established here: 3GPP TS 36.211 v13.2.0, "E-UTRA, Physical channels and modulation"; 3GPP TS 36.212 v13.2.0, "E-UTRA, Multiplexing and Channel coding"; 3GPP TS
[0018] [0018] To meet the demand for increased wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called "beyond the 4G network" or "post-LTE system".
[0019] [0019] The 5G communication system is provided to be implemented in higher frequency bands (mmWave), for example, 60GHz bands, to obtain higher data rates. To decrease the loss of radio wave propagation and increase the transmission coverage, the beam formation, the massive multiple inputs (MIMO), the full-size MIMO (FD-MIMO), the matrix antenna, a formation analog beam, large-scale antenna techniques and the like are discussed in 5G communication systems.
[0020] [0020] In addition, in 5G communication systems, development for system network enhancement is underway based on small advanced cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication ), wireless backhaul communication, mobile network, cooperative communication, coordinated multipoint transmission and reception (CoMP), interference mitigation and cancellation and the like.
[0021] [0021] In the 5G system, hybrid frequency switching and quadrature amplitude modulation (FQAM) and sliding window overlay coding (SWSC) as an adaptive modulation and coding technique (AMC), and filter bank multiport (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology were developed.
[0022] [0022] FIGURES 1-4B below describe various modalities implemented in wireless communication systems and with the use of orthogonal frequency division (OFDM) multiplexing or orthogonal frequency division (OFDMA) multiple access techniques. The descriptions in FIGURES 1-3 do not mean physical or architectural limitations to the way in which different modalities can be implemented. Different modalities of this disclosure can be implemented in any properly arranged communications system.
[0023] [0023] FIGURE 1 illustrates an example of a wireless network according to the modalities of the present disclosure. The wireless network mode shown in FIGURE 1 is illustrative only. Other modalities of the wireless network 100 may be used without departing from the scope of this disclosure.
[0024] [0024] As shown in FIGURE 1, the wireless network includes an eNB 101, an eNB 102, and an eNB 103. eNB 101 communicates with eNB 102 and eNB 103. eNB 101 also communicates with at least a network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or another data network.
[0025] [0025] eNB 102 provides wireless broadband access to network 130 for a first plurality of UEs within a coverage area 120 of eNB 102. The first plurality of UEs includes a UE 111, which can be located in a small company (SB); a UE 112, which can be located in a company (E); an UE 113, which can be located in a WiFi access point (HS); an UE 114, which can be located in a first residence (R); an UE 115, which can be located in a second residence (R); and an UE 116, which can be a mobile device (M), such as a cell phone, a wireless laptop, a wireless PDA, or the like. ENB 103 provides wireless broadband access to network 130 for a second plurality of UEs within a coverage area 125 of eNB 103. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more more than 101-103 eNBs can communicate with each other and with UEs 111-
[0026] [0026] Depending on the type of network, the term "base station" or "BS" can refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmission point (TP), transmit and receive (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wireless-enabled devices. Base stations can provide wireless access according to one or more wireless communication protocols, for example, new 5G 3GPP radio interface / access (NR), long-term evolution (LTE), advanced LTE (LTE-A) , access to high speed packets (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For the sake of convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. In addition, depending on the type of network, the term "user equipment" or "UE" can refer to any component, such as "mobile station", "subscriber station", "remote terminal", "wireless terminal", "receiving point", or "user device". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, regardless of whether the UE is a mobile device (such as a telephone cell phone or smartphone) or is normally considered a stationary device (such as a desktop computer or a vending machine).
[0027] [0027] The dotted lines show the approximate spans of coverage areas 120 and 125, which are shown as approximately circular only for purposes of illustration and explanation. It should be clearly understood that the coverage areas associated with eNBs, such as coverage areas 120 and 125, can take other forms, including irregular shapes, depending on the configuration of the eNBs and variations in the radio environment associated with natural and man-made obstructions. human beings.
[0028] [0028] As described in more detail below, one or more of the UEs 111-116 includes circuits, programming or a combination thereof, for efficient indication of the SS / PBCH block frequency location. In certain embodiments, and one or more of the eNBs 101-103 include circuits, programming, or a combination thereof, for efficient indication of SS / PBCH block frequency location.
[0029] [0029] Although FIGURE 1 illustrates an example of a wireless network, several changes can be made in FIGURE 1. For example, the wireless network can include any number of eNBs and any number of UEs in any suitable arrangement. In addition, eNB 101 can communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Likewise, each eNB 102-103 can communicate directly with network 130 and provide UEs wireless broadband access direct to network 130. In addition, eNBs 101, 102 and / or 103 can provide access to other networks or additional external networks, such as external telephone networks or other types of data networks.
[0030] [0030] FIGURE 2 illustrates an example of eNB 102 according to the modalities of the present disclosure. The eNB modality
[0031] [0031] As shown in FIGURE 2, the eNB 102 includes multiple antennas 205a-205n, multiple RF transceivers 210a-210n, transmission processing circuits (TX) 215 and receiving processing circuits (RX) 220. The eNB 102 it also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.
[0032] [0032] RF transceivers 210a-210n receive, from antennas 205a-205n, incoming RF signals, as signals transmitted by UEs on network 100. RF transceivers 210a-210n downwardly convert RF signals received to generate IF or baseband signals. The IF or baseband signals are sent to the RX 220 processing circuit, which generates processed baseband signals by filtering, decoding and / or digitizing the baseband or IF signals. The RX 220 processing circuit transmits the processed baseband signals to the controller / processor 225 for further processing.
[0033] [0033] The TX 215 processing circuit receives analog or digital data (such as voice data, web data, email, or interactive video game data) from the controller / processor 225. The TX 215 processing circuit encodes, multiplexes and / or digitizes the output baseband data to generate processed baseband or IF signals. RF transceivers 210a-210n receive the processed baseband or IF signals output from the TX 215 processing circuit and upwardly converts the baseband or IF signals into RF signals that are transmitted by the antennas 205a-205n.
[0034] [0034] Controller / processor 225 may include one or more processors or other processing devices that control the overall operation of eNB 102. For example, controller / processor 225 may control the receipt of direct channel signals and the transmission of signals reverse channel by RF transceivers 210a-210n, processing circuit RX 220, and processing circuit TX 215 according to well-known principles. The 225 controller / processor can also support additional functions, such as more advanced wireless communication functions. For example, controller / processor 225 can support beamforming or directional routing operations in which the output signals from multiple antennas 205a-205n are weighted differently to effectively direct the output signals in the desired direction. Any of a wide variety of other functions could be supported on the eNB 102 by the controller / processor 225.
[0035] [0035] Controller / processor 225 is also capable of executing programs and other processes resident in memory 230, such as an OS (operating system). Controller / processor 225 can move data into or out of memory 230, as required by an execution process.
[0036] [0036] The controller / processor 225 is also coupled to the backhaul or network interface 235. The backhaul or network interface 235 allows the eNB 102 to communicate with other devices or systems through a backhaul connection or through a network. The 235 interface can support communications over any suitable wired or wireless connection. For example, when eNB 102 is implemented as part of a cellular communication system (such as one that supports 5G, LTE or LTE-A), interface 235 can allow eNB 102 to communicate with other eNBs over a network connection. wired or wireless backhaul. When eNB 102 is implemented as an access point, interface 235 can allow eNB 102 to communicate over a wired or wireless LAN or through a wired or wireless connection to a larger network (such as the Internet) . The 235 interface includes any suitable structure that supports communications over a wired or wireless connection, such as an RF or Ethernet transceiver.
[0037] [0037] Memory 230 is coupled to controller / processor 225. Part of memory 230 may include RAM, and another part of memory 230 may include Flash memory or another ROM.
[0038] [0038] Although FIGURE 2 illustrates an example of eNB 102, several changes can be made in FIGURE 2. For example, eNB 102 can include any number of each component shown in FIGURE 2. As a particular example, an access point it can include a number of interfaces 235, and controller / processor 225 can support routing functions to route data between different network addresses. As another particular example, while shown to include a single instance of the TX 215 processing circuit and a single instance of the RX 220 processing circuit, the eNB 102 may include multiple instances of each
[0039] [0039] FIGURE 3 illustrates an example of UE 116 according to the modalities of the present disclosure. The embodiment of UE 116 illustrated in FIGURE 3 is for illustration only, and UEs 111-115 of FIGURE 1 can have the same or similar configuration. However, UEs come in a wide variety of configurations, and FIGURE 3 does not limit the scope of the present disclosure to any specific implementation of a UE.
[0040] [0040] As shown in FIGURE 3, the UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a processing circuit TX 315, a microphone 320, and a receiving processing circuit (RX) 325. The UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, a touch screen 350, a display 355, and a 360 memory. The 360 memory includes a system operating system (OS) 361 and one or more applications 362.
[0041] [0041] The RF transceiver 310 receives, from the antenna 305, an incoming RF signal transmitted by an eNB of the network 100. The RF transceiver 310 downwardly converts the incoming RF signal to generate a signal from intermediate frequency (IF) or base band. The IF or baseband signal is sent to the RX 325 processing circuit, which generates a processed baseband signal by filtering, decoding and / or digitizing the baseband or IF signal. The RX 325 processing circuit transmits the processed baseband signal to speaker 330 (as for voice data) or processor 340 for further processing (as for web browsing data).
[0042] [0042] The TX 315 processing circuit receives analog or digital voice data from microphone 320 or other output baseband data (such as web data, email, or interactive video game data) from processor 340. The circuit from TX 315 processing encodes, multiplexes and / or digitizes the output baseband data to generate a processed baseband or IF signal. The RF transceiver 310 receives the processed baseband or IF signal output from the TX 315 processing circuit and upwardly converts the baseband or IF signal to an RF signal that is transmitted through antenna 305.
[0043] [0043] Processor 340 can include one or more processors or other processing devices and run OS 361 stored in memory 360 in order to control the overall operation of UE 116. For example, processor 340 can control the receipt of direct channel and reverse channel signal transmission by RF transceiver 310, processing circuit RX 325, and processing circuit TX 315 according to well-known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.
[0044] [0044] Processor 340 is also capable of executing other processes and programs residing in 360 memory, such as processes for reporting CSI in PUCCH. Processor 340 can move data into or out of memory 360, as required by an execution process. In some embodiments, processor 340 is configured to run applications 362 based on OS 361 or in response to signals received from eNBs or an operator. The 340 processor is also coupled to the 345 I / O interface, which provides the UE 116 with the ability to connect to other devices, such as laptops and handhelds. The 345 I / O interface is the communication path between these accessories and the 340 processor.
[0045] [0045] Processor 340 is also coupled to the 350 touch screen and 355 display. The UE 116 operator can use the 350 touch screen to enter data into the UE 116. The 355 display can be a liquid crystal display , light-emitting diode display, or another display capable of rendering text and / or at least limited graphics, such as web sites.
[0046] [0046] The 360 memory is coupled to the 340 processor. Part of the 360 memory can include a random access memory (RAM), and another part of the 360 memory can include a Flash memory or other read-only memory (ROM).
[0047] [0047] Although FIGURE 3 illustrates an example of UE 116, several changes can be made in FIGURE 3. For example, several components in FIGURE 3 can be combined, further subdivided or omitted, and additional components can be added according to particular needs. As a particular example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In addition, while FIGURE 3 illustrates the UE 116 configured as a cell phone or smartphone, the UEs can be configured to operate as other types of mobile or stationary devices.
[0048] [0048] FIGURE 4A is a high level diagram of the transmission path circuits. For example, the transmission path circuit can be used for orthogonal frequency division (OFDMA) multiple access communication. FIGURE 4B is a high level diagram of the receiving path circuits. For example, the receiving path circuit can be used for orthogonal frequency division (OFDMA) multiple access communication. In FIGURES 4A and 4B, for downlink communication, the transmission path circuit can be implemented in a base station (eNB) 102 or in a relay station, and the receive path circuit can be implemented in a communication equipment. user (for example, user equipment 116 of FIGURE 1). In other examples, for uplink communication, the receiving path circuit 450 can be implemented at a base station (for example, eNB 102 of FIGURE 1) or at a relay station, and the transmission path circuit can be implemented on user equipment (for example, user equipment 116 of FIGURE 1).
[0049] [0049] The transmission path circuit comprises the 405 channel modulation and coding block, serial-to-parallel (S-to-P) block 410, Fast Fourier Inverse Transform (IFFT) block 415 Size N, block parallel-to-serial (P-to-S) 420, cyclic prefix addition block 425, and upstream converter (UC) 430. The receiving path circuit 450 comprises the downstream converter (DC) 455, removal block cyclic prefix 460, the serial-to-parallel (S-to-P) block 465, the Fast Fourier Transform (FFT) block 470 Size N, parallel-to-serial (P-to-S) block 475, and 480 channel demodulation and decoding block.
[0050] [0050] At least some of the components in FIGURES 4A 400 and 4B 450 can be implemented in software, while other components can be implemented by configurable hardware or a mixture of software and configurable hardware. In particular, note that the FFT blocks and IFFT blocks described in this disclosure document can be implemented as configurable software algorithms, where the value of size N can be modified according to the implementation.
[0051] [0051] In addition, although the present disclosure is directed to a modality that implements the Fast Fourier Transform and the Fast Inverse Fourier Transform, this is for illustrative purposes only and cannot be interpreted to limit the scope of the disclosure. It can be appreciated that, in an alternative embodiment of the present disclosure, the Fast Fourier Transform functions and the Fast Inverse Fourier Transform functions can be easily replaced by discrete Fourier transform (DFT) functions and discrete Fourier transform functions. inverse (IDFT), respectively. It can be considered that, for DFT and IDFT functions, the value of variable N can be any integer (that is, 1, 4, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N can be any integer with a power of two (that is,
[0052] [0052] In the transmission path circuit 400, the 405 channel modulation and coding block receives a set of information bits, applies coding (for example, LDPC coding) and modulates (for example, quadrature phase shift switching (QPSK) or quadrature amplitude modulation (QAM)) input bits to produce a sequence of modulation symbols in the frequency domain. The serial-to-parallel block 410 converts (ie demultiplexes) the symbols modulated in series into parallel data to produce N streams of parallel symbols where N is the IFFT / FFT size used in BS 102 and UE 116. The IFFT block of size N 415, then performs an IFFT operation on the N parallel symbol streams to produce time domain output signals. The parallel-to-serial block 420 converts (i.e., multiplexes) the output symbols in the parallel time domain of the IFFT block of size N 415 to produce a signal in the time domain in series. Add cyclic prefix block 425 and then insert a cyclic prefix in the signal in the time domain. Finally, the upstream converter 430 modulates (i.e. upwardly converts) the output of the cyclic prefix addition block 425 to the RF frequency for transmission over a wireless channel. The signal can also be filtered on the base band before converting to the RF frequency.
[0053] [0053] The transmitted RF signal arrives at UE 116 after passing through the wireless channel, and reverse operations are performed to those of eNB 102. Downward converter 455 downwardly converts the received signal into a base band frequency, the cyclic prefix removal 460 removes the cyclic prefix to produce the baseband signal in the serial time domain. The serial-to-parallel block 465 converts the baseband signal in the time domain into signals in the parallel time domain. The FFT block size N 470 then performs an FFT algorithm to produce N signals in the parallel frequency domain. The parallel-to-serial block 475 converts parallel signals in the frequency domain into a sequence of modulated data symbols. The channel demodulation and decoding block 480 demodulates and then decodes the modulated symbols to recover the original input data stream.
[0054] [0054] Each of the 101-103 eNBs can implement a transmission path that is analogous to transmitting on the downlink to user equipment 111-116 and can implement a receiving path that is analogous to receiving on the uplink of the user equipment. user 111-116. Likewise, each user equipment 111-116 can implement a transmission path corresponding to the architecture to transmit on the uplink to eNBs 101-103 and can implement a receiving path corresponding to the architecture to receive on the downlink of eNBs 101 -103.
[0055] [0055] The use cases of the 5G communication system have been identified and described. These use cases can be roughly categorized into three different groups. In one example, enhanced mobile broadband (eMBB) is determined to meet high bit / s requirements, with less stringent latency and reliability requirements. In another example, ultra reliable and low latency (URLL) is determined with less stringent bit / s requirements. In another example, massive machine-type communication (mMTC) is determined that a number of devices can be
[0056] [0056] A communication system includes a downlink (DL) that carries signals from transmission points such as base stations (BSs) or Nodes to user equipment (UEs) and an uplink (UL) that carries signals from the UEs to points of reception as NóBs. A UE, also commonly referred to as a mobile terminal or station, can be fixed or mobile and can be a cell phone, a personal computer device or an automated device. An eNodeB, which is usually a fixed station, can also be called an access point or other equivalent terminology. For LTE systems, a NodeB is often called an eNodeB.
[0057] [0057] In a communication system, such as the LTE system, DL signals can include data signals that carry information content, control signals that carry DL control information (DCI), and reference signals (RS) that they are also known as pilot signals. An eNodeB transmits data information through a physical DL shared channel (PDSCH). An eNodeB transmits DCI through a physical DL control channel (PDCCH) or an enhanced PDCCH (EPDCCH).
[0058] [0058] An eNodeB transmits confirmation information in response to the transmission of data transport block (TB)
[0059] [0059] DL signals also include the transmission of a logical channel that carries system control information. A BCCH is mapped to a transport channel referred to as a transmission channel (BCH) when the BCCH transports a master information block (MIB) or to a shared DL channel (DL-SCH) when the BCCH transports an information block from the system (SIB). Most of the system information is included in different SIBs transmitted using the DL-SCH. A presence of system information on a DL-SCH in a subframe can be indicated by a transmission from a corresponding PDCCH that carries a code word with a cyclic redundancy check (CRC) encrypted with special information from the RNTI system (SI-RNTI ). Alternatively, the scheduling information for a SIB transmission can be provided in a previous SIB and the scheduling information for the first SIB (SIB-1) can be provided by the MIB.
[0060] [0060] The allocation of DL resources is performed in a subframe unit and in a group of physical resource blocks (PRBs). A transmission BW includes frequency resource units called resource blocks (RBs). Each RB includes subcarriers or resource elements (REs), such as 12 REs. A unit of a RB on a subframe is referred to as PRB. A UE can be allocated in RDS of MPDSCH for a total of REs for the PDSCH transmission BW.
[0061] [0061] UL signals can include data signals that carry data information, control signals that carry UL control information (UCI), and UL RS. UL RS includes DMRS and RS Polling (SRS). A UE transmits DMRS only in a BW of the respective PUSCH or PUCCH. An eNodeB can use a DMRS to demodulate data signals or UCI signals. A UE transmits SRS to provide an eNodeB with a UL CSI. A UE transmits data or UCI information through a respective physical UL shared channel (PUSCH) or a physical UL control channel (PUCCH). If a UE needs to transmit data and UCI information in the same UL subframe, the UE can multiplex both into a PUSCH. The UCI includes hybrid auto-repeat request confirmation information (HARQ-ACK), indicating correct (ACK) or incorrect (NACK) detection for a TB of data in a PDSCH or absence of a PDCCH (DTX) detection, escalation request (SR) indicating whether a UE has data in temporary storage, in the classification indicator (RI),
[0062] [0062] A UL subframe includes two slots. Each slot includes symbols to transmit data information, UCI, DMRS, or SRS. A frequency resource unit of a UL system BW is an RB. One UE is allocated in NRB RBs for a total of REs for a transmitting BW. For a PUCCH, NRB = 1. A last subframe symbol can be used to multiplex SRS transmissions from one or more UEs. A number of subframe symbols that are available for data transmission / UCI / DMRS are, where if a last subframe symbol is used to transmit SRS and otherwise.
[0063] [0063] FIGURE 5 illustrates a block diagram of transmitter 500 for a PDSCH in a subframe according to the modalities of the present disclosure. The block diagram mode of the transmitter 500 illustrated in FIGURE 5 is for illustration only. FIGURE 5 does not limit the scope of the present disclosure to any specific implementation of the transmitter 500 block diagram.
[0064] [0064] As shown in FIGURE 5, information bits 510 are encoded by encoder 520, as a turbo encoder, and modulated by modulator 530, for example, using quadrature phase shift (QPSK) switching modulation. A 540 serial-to-parallel (S / P) converter generates M modulation symbols that are subsequently supplied to a 550 mapper to be mapped to REs selected by a 555 transmit BW selection unit to an assigned PDSCH transmit BW, the unit 560 applies a Fast Inverse Fourier Transform (IFFT), the output is then serialized by a 570 parallel-to-serial converter (P / S) to create a time domain signal, filtering is applied by the 580 filter, and a transmitted 590 signal. Additional features, such as data encryption, cyclic prefix insertion, time window, interleaving, and others are well known in the art and are not shown for brevity.
[0065] [0065] FIGURE 6 illustrates a receiving block diagram 600 for a PDSCH in a subframe according to the modalities of the present disclosure. The embodiment of diagram 600 shown in FIGURE 6 is for illustration only. FIGURE 6 does not limit the scope of the present disclosure to any specific implementation of diagram 600.
[0066] [0066] As shown in FIGURE 6, a received signal 610 is filtered through filter 620, REs 630 for an assigned receive BW are selected by the BW selector 635, unit 640 applies a Fast Fourier Transform (FFT), and an output is serialized by a parallel-to-serial converter
[0067] [0067] FIGURE 7 illustrates a block diagram of transmitter 700 for a PUSCH in a subframe according to the modalities of the present disclosure. The block diagram embodiment 700 shown in FIGURE 7 is for illustration only. FIGURE 7 does not limit the scope of the present disclosure to any specific implementation of block diagram 700.
[0068] [0068] As shown in FIGURE 7, information data bits 710 are encoded by encoder 720, as a turbo encoder, and modulated by modulator 730. A discrete Fourier Transform (DFT) unit 740 applies a DFT to the modulated data, REs 750 corresponding to an assigned PUSCH transmission BW are selected by the transmission BW selection unit 755, unit 760 applies an IFFT and, after a cyclic prefix insertion (not shown), filtering is applied by the filter 770 and a transmitted signal 780.
[0069] [0069] FIGURE 8 illustrates a receiver block diagram 800 for a PUSCH in a subframe according to the modalities of the present disclosure. The embodiment of the block diagram 800 illustrated in FIGURE 8 is for illustration only. FIGURE 8 does not limit the scope of the present disclosure to any specific implementation of block diagram 800.
[0070] [0070] As shown in FIGURE 8, a received signal 810 is filtered by filter 820. Subsequently, after removing a cyclic prefix (not shown), the unit 830 applies an FFT, the REs 840 corresponding to a PUSCH receiving BW assigned are selected by a receiving BW selector 845, unit 850 applies an inverse DFT (IDFT), a demodulator 860 consistently demodulates data symbols by applying a channel estimate obtained from a DMRS (not shown), a decoder 870, like a turbo decoder, it decodes the demodulated data to provide an estimate of the 880 information data bits.
[0071] [0071] In the next generation cellular systems, several use cases are anticipated in addition to the resources of the LTE system. Called 5G or fifth generation cellular system, a system capable of operating at sub-6GHz and above 6 GHz (for example, in the mmWave regime) becomes one of the requirements. In 3GPP TR 22,891, 74 5G use cases were identified and described; these use cases can be roughly categorized into three different groups. A first group is called 'enhanced mobile broadband' (eMBB), aimed at high data rate services with less stringent latency and reliability requirements. A second group is called "ultra-reliable and low latency (URLL)" aimed at applications with less stringent data rate requirements, but less tolerant to latency. A third group is called "massive MTC (mMTC)" targeting a large number of low power device connections, such as 1 million per km², with less stringent requirements for reliability, data rate and latency.
[0072] [0072] For the 5G network to support services as diverse with different quality of service (QoS), a modality was identified in the LTE specification, called network slicing. To use PHY resources efficiently and multiplex multiple slices (with different resource allocation schemes, numerologies, and scheduling strategies) in the DL-SCH, a flexible and autonomous frame or subframe design is used.
[0073] [0073] Energy consumption and battery life are very important for the terminals of an Internet of Things (IoT). In a narrowband IoT system (NB-IoT) or an enhanced machine-type communication system (eMTC), the power of terminal devices can be saved by configuring a power saving mode (PSM) or an extended discontinuous reception mode (eDRX). However, an UE is unable to hear paging messages during suspension in PSM mode or eDRX mode. In some IoT application scenarios, a UE is required to establish a connection to a network within a certain period of time after receiving a network command. So the UE that has the requirement cannot be configured with PSM mode or eDRX mode that has a relatively long period.
[0074] [0074] In NB-IoT and an enhanced version of the eMTC system, to enable a UE to be paged, and in the meantime, save energy, an activation / suspension signal / channel is introduced after study and research. The activation signal / channel is configured to activate a UE, that is, a case where the UE needs to continue monitoring a subsequent MTC physical downlink control channel (MPDCCH) used to indicate a paging message. The suspend signal / channel is configured to instruct that a UE can enter a suspend state, that is, a case in which the UE does not need to monitor a subsequent MPDCCH that is used to indicate a paging message.
[0075] [0075] In a multi-carrier system, a carrier that transmits a synchronization signal is called an anchor carrier and, in an LTE system, a paging signal is transmitted on an anchor carrier. In an NB-IoT system, a scheme for transmitting paging messages on non-anchor carriers is introduced. In the eMTC system, multiple narrow bands are defined, in which a narrow band has 6 blocks of physical resources (PRBs), and the concept of narrow band paging is introduced. In addition, in the eMTC system, a downlink control channel for MTC, MPDCCH, is configured to indicate a paging message, and different UEs can monitor MPDCCHs in different narrow bands. Likewise, in a new 5G radio system (NR) in progress, there is a situation where the bandwidth of a UE is less than the bandwidth of the system, in which case, multiple parts of the bandwidth can be defined for a paging channel. For multi-carrier or narrow bands or partial bandwidths, it is still a problem to be solved on how to transmit and receive an activation or suspend signal.
[0076] [0076] FIGURE 9 illustrates an example of positions in time domain 900 for mapping PSS / SSS to FDD and TDD according to the modalities of the present disclosure. The mode of time domain positions 900 illustrated in FIGURE 9 is for illustration only. FIGURE 9 does not limit the scope of this disclosure to any specific implementation.
[0077] [0077] With reference to FIGURE 9, in the case of FDD, in all frames (905), a PSS (925) is transmitted within the last symbol of a first slot in subframes 0 and 5 (910 and 915), in that a subframe includes two slots. An SSS (920) is transmitted within the second last symbol of the same slot. In the case of TDD, in all frames (955), a PSS (990) is transmitted within a third symbol of subframes 1 and 6 (965 and 980), while a (SSS) 985 is transmitted in a last symbol of subframes 0 and 5 (960 and 970). The difference allows the detection of the duplex scheme in a cell. Resource elements for PSS and SSS are not available for transmitting any other type of DL signal.
[0078] [0078] In the present disclosure, for the sake of brevity, both FDD and TDD are considered as the duplex method for both DL and UL signaling. Although exemplary descriptions and modalities below assume orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), the present disclosure can be extended to other transmission waveforms based on OFDM or access schemes multiple, such as filtered OFDM (F-OFDM).
[0079] [0079] This disclosure covers several components that can be used together or in combination with each other, or can operate as independent schemes.
[0080] [0080] A communication system includes a downlink (DL) that carries signals from transmission points such as base stations (BSs) or Nodes to user equipment (UEs) and an uplink (UL) that carries signals from UEs to points of reception as NóBs. A UE, also commonly referred to as a mobile terminal or station, can be fixed or mobile and can be a cell phone, a personal computer device or an automated device. An eNodeB, which is usually a fixed station, can also be called an access point or other equivalent terminology. For LTE systems, a NodeB is often called an eNodeB. For NR systems, a NodeB is often called gNóB.
[0081] [0081] In the present disclosure, numerology refers to a set of signal parameters that can include subframe duration, subcarrier spacing, cyclic prefix length, transmission bandwidth, or any combination of these signal parameters.
[0082] [0082] For initial LTE access, primary and secondary synchronization signals (PSS and SSS, respectively) are used for time and coarse frequency synchronization and cell ID acquisition. As the PSS / SSS is transmitted twice per 10ms radio frame and the enumeration in the time domain is introduced in terms of the system frame number (SFN, included in the MIB), frame timing is detected in the PSS / SSS to avoid the need to increase the PBCH detection responsibility. In addition, the cyclic prefix length (CP) and, if unknown, the duplexing scheme can be detected on the PSS / SSS.
[0083] [0083] The PSS is constructed from a ZC sequence in the frequency domain of length 63, with the truncated middle element to avoid the use of d.c. subcarrier. Three roots are selected for the PSS to represent the three physical layer identities within each group of cells. SSS strings are based on the maximum length strings (also known as M-strings).
[0084] [0084] Each SSS sequence is constructed by interleaving two sequences modulated with BPSK of length 31 in the frequency domain, where the two source sequences before modulation are different cyclical changes of the same M-sequence. Cyclic change indices are constructed from the physical cell ID group. Since the PSS / SSS detection can be defective (due to, for example, non-idealities in the PSS / SSS auto-cross-correlation properties and lack of CRC protection), the cell ID hypotheses detected from the PSS / SSS may occasionally confirmed by PBCH detection.
[0085] [0085] The PBCH is used mainly to signal the Master Block Information (MIB), which consists of DL and UL system bandwidth information (3 bits), PHICH information (3 bits), and SFN (8 bits). Adding 10 reserved bits (for other uses, such as MTC), the MIB's payload is 24 bits. After being attached to a 16-bit CRC, a 1/3 tail-biting rate convolutional encoding, 4x repetition, and QPSK modulation are applied to the 40-bit codeword. The resulting stream of QPSK symbols is transmitted by 4 subframes spread over 4 radio frames. In addition to detecting the MIB, blind detection of the number of CRS ports is also required for the PBCH.
[0086] [0086] For the licensed NR spectrum, each synchronization and PBCH signal block (SS / PBCH block) comprise of a symbol for NR-PSS, two symbols for NR-PBCH, a symbol for NR-SSS and NR-PBCH, where the four symbols are mapped consecutively and multiplexed by time division. NR-SS is a unified project, including the NR-PSS and NR-SSS sequence design, for all carrier frequency ranges supported in NR. The transmission bandwidth of NR-PSS and NR-SSS (for example, 12 PRBs) is less than the transmission bandwidth of the entire SS / PBCH block (for example, 20 PRBs). For the initial selection of cells for the NR cell, the UE assumes the periodicity of the standard burst SS set as 20 ms, and to detect the non-independent NR cell, the network provides periodicity information for the burst SS set by frequency carrier for the UE and information to derive the time / duration of the measurement if possible.
[0087] [0087] The control feature set (CORESET) to receive common control channels, such as RMSI, OSI, SIBx, RAR etc., is required to be configured. According to recent 3GPP RAN1 agreements, one CORESET configuration is provided via PBCH (or MIB) for at least RMSI scaling, and another CORESET configuration is provided via RMSI (or SIB1) for at least RAR scaling. A CORESET (set of control features) can be characterized by the slot time, OFDM symbol numbers in each slot, and frequency features. These CORESET properties are indicated or pre-configured for each CORESET.
[0088] [0088] For RMSI / SIB scheduling, CORESET properties are provided in the PBCH. For RAR scheduling, CORESET properties are provided in the RMSI. Among these CORESET properties configured by PBCH / RMSI, OFDM symbol numbers and frequency features can be commonly applicable to all common channels (eg SIBx / RAR, etc.), but slot timing can be determined specifically for different SIBx / RAR. In NR, multiple SS / PBCH blocks within a broadband carrier are supported, and some of the SS / PBCH blocks on the same carrier may not all be associated with an RMSI. For SS / PBCH blocks without associated RMSI, a code point in the PRB grid shift indication (for example, 4 bits for> 6 GHz and 5 bits for <6 GHz) is used to indicate the absence of RMSI, and in an example, the 8 bits for RMSI CORESET and the configuration of the search space in the MIB can be used for other purposes.
[0089] [0089] This disclosure considers the use of 8 bits for RMSI CORESET and the configuration of the search space in the MIB, potentially together with other fields or reserved code points, when no associated RMSI is indicated.
[0090] [0090] In one embodiment, when multiple SS / PBCH blocks are supported on a broadband, at least one of the SS / PBCH blocks can be located on the preset synchronization scans to define a cell for initial access purposes. For SS / PBCH blocks, which may or may not be associated with an RMSI, and whether or not there is an associated RMSI, it is indicated by a code point in the PRB grid offset indication. If a UE successfully detects the SS / PBCH block in a synchronization scan, and still detects that there is no RMSI associated with the SS / PBCH block, the UE can use the field, for example, 8 bits, which are originally used for configurations ISMS, to indicate the exact location of the next or other SS / PBCH blocks, so that the UE can skip some of the synchronization scan locations to search blindly.
[0091] [0091] In a sub-mode, some other field in the PBCH content or some reserved code point of other fields in the PBCH content can be combined with the 8 bits of the RMSI CORESET configuration to obtain a larger indication range. For example, if an extra bit can be combined, the indication range can be increased to 511 or 512 (depending on which code point indicates no cell definition SS / PBCH block in the band). For another example, if a maximum of 4 other reserved code points can be combined, the indication range can be increased to 1023 or 1024 (depending on which code point indicates no cell definition SS / PBCH block in the band) .
[0092] [0092] In one embodiment, the exact location of the synchronization scan where the next SS / PBCH block associated with an RMSI can be located, where each of the code points represents an exact location of a synchronization scan where an SS block / PBCH can be found. After decoding the code point, the UE can directly find the frequency location of the synchronization scan that the UE can search for.
[0093] [0093] For a sub-mode, the location relative to the synchronization scan with a detected SS / PBCH block is measured by the number of synchronization scans, where the number is always non-negative, which means that the relative location is always defined along the initial cell search order within the band. The code point defining the relative location "0" of the next SS / PBCH block is essential, since the code point can indicate that within the indication capability (for example, for a bandwidth of 255 synchronization scans using the 8 bits), there is no cell definition SS / PBCH block with the associated ISMS, and the UE can skip all possible sync scans within the search range and continue to perform the blind scan of the first sync scan with the relative location that exceeded the search range for the current SS / PBCH block. Table 1 Configuration index in dcch- GSCN for cell ConfigSIB1 definition SS / PBCH block 0 No cell definition SS / PBCH block in search range 1 GSCN-Current + 1 2 GSCN-Current +2 ... .. .
[0094] [0094] In TABLE 1, GSCN-Current is the value of the global synchronization channel number (GSCN) for the current SS / PBCH block which is indicated that no ISMS has. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer parameter ssb- SubcarrierOffset receives the value of {r_0, r_1, r_2, r_3}, and the UE can assume the mapping from pdcch-ConfigSIB1 to the GSCN of the synchronization scan that the UE can search for the cell definition SS / PBCH block within the search band is in accordance with TABLE 1 and a UE assumes that there is no cell definition SS / PBCH block in the GSCN range - Current up to GSCN-Current +255 if pdcch-ConfigSIB1 = 0.
[0095] [0095] Note that TABLE 1 can be provided in an equivalent way by a formula. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb-SubcarrierOffset parameter receives the value of {r_0, r_1, r_2, r_3}, which corresponds to the index-
[0096] [0096] In TABLE 2, GSCN-Current is the GSCN value for the current SS / PBCH block which is indicated that no RMSI has. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb-SubcarrierOffset parameter receives the value of {r_0, r_1, r_2, r_3}, and the UE can assume the mapping of ssb-SubcarrierOffset and pdcch-ConfigSIB1 for the GSCN of the synchronization scan that the UE can search for the cell definition SS / PBCH block within the search band is in accordance with TABLE 2, and the UE does not assume any cell definition SS / PBCH block cell in the range GSCN-Current to GSCN-Current +1023 if {ssb-SubcarrierOffset, pdcch-ConfigSIB1} = {r_0, 0}.
[0097] [0097] Note that TABLE 2 can be provided in an equivalent way by a formula. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb-SubcarrierOffset parameter receives the value of {r_0, r_1, r_2, r_3}, which corresponds to the index- reserved-ssb-SubcarrierOffset receiving the value of {0, 1, 2, 3}, respectively, and the UE can assume the GSCN of the synchronization scan that the UE can search for the cell definition SS / PBCH block within the search band is calculated according to GSCN-cell-defined-SSB = GSCN-Current + 256 * index-reserved-ssb-SubcarrierOffset + pdcch-ConfigSIB1, when {index-reserved-ssb-SubcarrierOffset, pdcch- ConfigSIB1} {0, 0}; and the UE does not assume any cell definition SS / PBCH blocks in the GSCN-Current range until GSCN-Current + 1023 if {index-reserved-ssb-SubcarrierOffset, pdcch- ConfigSIB1} = {0, 0}, where GSCN- cell-defined-SSB is the GSCN for the next SS / PBCH block defined by cell, GSCN- Current is the GSCN value of the current SS / PBCH block which is indicated that no ISMS has, index-reserved-ssb- SubcarrierOffset is the index of the code point reserved in ssb-SubcarrierOffset (receiving value of {0,1,2,3}) and pdcch- ConfigSIB1 is receiving value of {0,1, ..., 254,255}.
[0098] [0098] In another sub-mode, the location relative to the synchronization scan with a detected SS / PBCH block is measured by the number of synchronization scans (that is, GSCN values), where the number can be positive or negative to define the relative location on one side of the SS / PBCH block. In one example, a code point that defines the relative location "0" of the next SS / PBCH block may indicate that within the indication capability (for example, for a bandwidth of 255 synchronization scans using the 8 bits), there is no SS / PBCH synchronization with the associated ISMS, and the UE can skip all synchronization scans within the table and continue to perform blind search on the remaining synchronization scans.
[0099] [0099] In one example, more code points may indicate no cell definition SS / PBCH blocks within a range, where the range is provided by the GSCN index (for example, the beginning and end of the GSCN). Table 3 Configuration index in pdcch- GSCN for SS / PBCH block defining ConfigSIB1 cell 0 No SS / PBCH block defining cell in search range 1 GSCN-Current + 1 2 GSCN-Current + 2 ... .. .
[00100] [00100] In TABLE 3, GSCN-Current is the GSCN value of the current SS / PBCH block which is indicated that no ISMS presents. In the initial cell selection, a UE can assume that no associated ISMS presents if the upper layer ssb-SubcarrierOffset parameter receives the value of {r_0, r_1, r_2, r_3}, and the UE can assume the mapping from pdcch-ConfigSIB1 to the GSCN of the synchronization scan that the UE can search for the cell definition SS / PBCH block within the search range is according to TABLE 3, and the UE does not assume any cell definition SS / PBCH block in the GSCN range -Current -128 to GSCN-Current +127 if pdcch-ConfigSIB1 = 0.
[00101] [00101] Note that TABLE 3 can be provided in an equivalent way by a formula.
[00102] [00102] In Table 4, GSCN-Current is the GSCN value for the current SS / PBCH block which is indicated that no ISMS presents. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb-SubcarrierOffset parameter receives the value of {r_0, r_1, r_2, r_3}, and the UE can assume the mapping of ssb-SubcarrierOffset and pdcch-ConfigSIB1 for the GSCN of the sync scan that the UE can search for the cell definition SS / PBCH block within the search band is in accordance with Table 4, and the UE does not assume any cell definition SS / PBCH block cell in the range GSCN-Current -512 to GSCN-Current +511 if {ssb-SubcarrierOffset, pdcch-ConfigSIB1} = {r_0, 0}.
[00103] [00103] Note that Table 4 can be provided in an equivalent way by a formula. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb-SubcarrierOffset parameter receives the value of {r_0, r_1, r_2, r_3}, which corresponds to index-reserved-ssb-SubcarrierOffset receiving the value of {0, 1, 2, 3}, respectively, and the UE can assume the GSCN of the synchronization scan that the UE can search for the cell definition SS / PBCH block within the search band is calculated according to GSCN-cell- defined-SSB = GSCN-Current + 256 * index-reserved-ssb- SubcarrierOffset + pdcch-ConfigSIB1, when reserved-ssb- SubcarrierOffset <2 and {index-reserved-ssb-SubcarrierOffset, pdcch-ConfigSIB1} {0, 0}; GSCN-cell-defined-SSB = GSCN- Current - 256 * (index-reserved-ssb-SubcarrierOffset-2) - pdcch-ConfigSIB1, when index- reserved-ssb- SubcarrierOffset> 1; and the UE does not assume any cell definition SS / PBCH blocks in the range GSCN-Current -512 to GSCN- Current +511 if {index-reserved-ssb-SubcarrierOffset, pdcch- ConfigSIB1} = {0, 0}, where GSCN-cell-defined-SSB is the GSCN for the next SS / PBCH block defined by cell, GSCN- Current is the GSCN value for the current SS / PBCH block which is indicated that no RMSI has, index-reserved-ssb- SubcarrierOffset is the index of the reserved code point in ssb-SubcarrierOffset (receiving the value of {0, 1, 2, 3}) and pdcch-ConfigSIB1 is receiving the value of {0, 1, ..., 254,
[00104] [00104] In TABLES 5 and 6, GSCN-Current is the GSCN value for the current SS / PBCH block that is indicated that no ISMS presents. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb- SubcarrierOffset parameter receives the value of {12,13,14,15} (or equivalently {r_0, r_1, r_2, r_3}) and the UE can assume the mapping of ssb-SubcarrierOffset, (for FR1 only) and pdcch-ConfigSIB1 to the synchronization scan GSCN that the UE can search for the cell definition SS / PBCH block within the search band is in agreement with TABLES 5 and 6, and the UE does not assume any cell definition SS / PBCH blocks in the given range if ssb- SubcarrierOffset = 14 or 15.
[00105] [00105] Note that TABLES 5 and 6 can be given in an equivalent way by a formula. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb-SubcarrierOffset parameter receives the value of {12, 13, 14, 15} (or equivalently {r_0, r_1, r_2, r_3}) and the UE can assume the GSCN of the synchronization scan that the UE can search for the cell definition SS / PBCH block within the search band is calculated according to the GSCN-cell-defined-SSB = GSCN-Current + 256 * + pdcch-ConfigSIB1 + 1, when ssb- SubcarrierOffset = 12; GSCN-cell-defined-SSB = GSCN-Current - 256 * - pdcch-ConfigSIB1-1, when ssb-SubcarrierOffset = 13; and the UE does not assume any cell definition SS / PBCH blocks in the GSCN-Current range - (512 * + 256 * (ssb- SubcarrierOffset-14) + pdcch-ConfigSIB1) / 32 to GSCN-Current + (512 * + 256 * (ssb-SubcarrierOffset-14) + pdcch-ConfigSIB1)
[00106] [00106] In TABLES 7 and 8, GSCN-Current is the GSCN value for the current SS / PBCH block which is indicated that no ISMS presents. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb- SubcarrierOffset parameter receives the value of {12, 13, 14, 15} for FR2 or receives the value {8, 9, 10, 11, 12, 13, 14, 15} with = 1 for FR1 (equivalent to k_SSB receiving the value of {12, 13, 14, 15} for FR2 and {24, 25, 26, 27, 28, 29, 30 , 31} for FR1, respectively), and the UE can assume the mapping of ssb-SubcarrierOffset, (for FR1 only) and pdcch-ConfigSIB1 to the synchronization scan GSCN that the UE can search for the SS / PBCH block of definition of cell within the search band is in accordance with TABLES 7 and 8, and the UE does not assume any cell definition SS / PBCH blocks in the range provided from GSCN- Current - pdcch-ConfigSIB1 / 16 to GSCN-Current + pdcch- ConfigSIB1 mod 16 if ssb-SubcarrierOffset = 15 for FR2 and ssb- SubcarrierOffset = 15 and = 1 for FR1.
[00107] [00107] Note that TABLES 7 and 8 can be given in an equivalent way by a formula. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb-SubcarrierOffset parameter receives the value of {12, 13, 14, 15} for FR2 or receives the value {8, 9, 10, 11, 12, 13, 14, 15} with = 1 for FR1 (equivalent to k_SSB receiving the value of {12, 13, 14, 15} for FR2 and {24, 25, 26, 27, 28, 29, 30 , 31} for FR1, respectively), and the UE can assume the GSCN of the synchronization scan that the UE can search for the cell definition SS / PBCH block within the search band is calculated according to FR1 GSCN-cell- defined-SSB = GSCN-Current + 256 * (ssb-SubcarrierOffset-8) + pdcch- ConfigSIB1 + 1, when = 1 and ssb-SubcarrierOffset = 8 or 9 or 10; GSCN-cell-defined-SSB = GSCN-Current - 256 * (ssb-
[00108] [00108] In TABLES 9 and 10, GSCN-Current is the GSCN value for the current SS / PBCH block which is indicated that no ISMS has. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb- SubcarrierOffset parameter receives the value of {12,13,14,15} (or equivalently {r_0, r_1, r_2, r_3}) and the UE can assume the mapping of ssb-SubcarrierOffset, (for FR1 only) and pdcch-ConfigSIB1 to the synchronization scan GSCN that the UE can search for the cell definition SS / PBCH block within the search band is in agreement with TABLES 9 and 10, and the UE does not assume any cell definition SS / PBCH blocks in the range provided from GSCN- Current - (* 256 + pdcch-ConfigSIB1) / 32 to GSCN-Current + (* 256 + pdcch-ConfigSIB1 ) mod 32 if ssb-SubcarrierOffset = 15 for FR1, and from GSCN-Current - ((ssb-SubcarrierOffset- 14) * 256 + pdcch-ConfigSIB1) / 32 to GSCN-Current + (((ssb- SubcarrierOffset-14) * 256 + pdcch-ConfigSIB1) mod 32 if ssb- SubcarrierOffset = 15 or 14 for FR2.
[00109] [00109] Note that TABLES 9 and 10 can be given in an equivalent way by a formula. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb-SubcarrierOffset parameter receives the value of {12, 13, 14, 15} (or equivalently {r_0, r_1, r_2, r_3}) and the UE can assume the GSCN of the synchronization scan that the UE can search for the cell definition SS / PBCH block within the search band is calculated according to FR1 GSCN-cell-defined-SSB = GSCN-Current + 256 * (ssb-SubcarrierOffset- 12) + pdcch-ConfigSIB1 + 1, when = 0 and ssb- SubcarrierOffset = 12 or 13, 14; GSCN-cell-defined-SSB =
[00110] [00110] In one embodiment, the 8 bits are used to indicate the frequency location range in which the next SS / PBCH block associated with an RMSI can be located, where each of the 256 code points represents a location range frequency at which an SS / PBCH block can be located. After decoding the 8 bits, the UE can go directly to the indicated frequency range and blindly search for all synchronization scans within the indicated range if there are multiple synchronization scans within the indicated range, and can directly search for the indicated synchronization scan. , if there is only a single sync scan within the indicated range.
[00111] [00111] In an example, in Table 11, for a given band, assuming the lowest carrier frequency as F_1 and the highest carrier frequency as F_2. The entire band is divided into 256 frequency location bands, possibly containing the synchronization scans, where the interval for each band is I_F = (F_2-F_1) / 255, and each of the 256 code points represents one of the frequency bands. frequency location. Table 11 Code point index Range of frequency locations that contain synchronization scan (s) 1 [F_1, F_1 + I_F) 2 [F_1 + I_F, F_1 + 2 * I_F) ... ...
[00112] [00112] In another example, in Table 12, for a given band, assuming the lowest carrier frequency as F_1, the highest carrier frequency as F_2, and the current location (on a synchronization scan) where the UE detects an SS / PBCH block without RMSI as F_S. The remainder of the band to be searched is divided into 256 frequency location bands, possibly containing the synchronization scans, where the interval for each band is I_F = (F_2-F_c) / 255 if the search order is assumed to be low to high in the frequency domain (I_F = (F_c- F_1) / 255 if the search order is assumed to be high to low in the frequency domain) and each of the 256 code points represents one of the location ranges of frequency. Table 12 Point index Range of locations of frequency code range that contain frequency that contain synchronization scan (s) scan (s) if the search order is synchronization if the low order for high search is high to low 1 [F_c, F_c + I_F) [F_c, F_c- I_F) 2 [F_c + I_F, F_c + 2 * I_F) [F_c- I_F, F_c- 2 * I_F) ... ... ... ...
[00113] [00113] In one mode, if there is only one synchronization scan within each indicated range (note that the divided range may not be uniform), the aforementioned modality is effectively equivalent as indicating the exact location of the synchronization scan in this band. Still, one of the code points can be used to indicate no cell definition SS / PBCH blocks within the band, and the code point can be a code point separate from those indicating the synchronization scan location, or be the location of the synchronization scan corresponding to the current search location in the frequency domain (that is, also in a synchronization scan).
[00114] [00114] In a sub-mode, if the synchronization scan number exceeds 255 for a band, some reserved bits in the PBCH content or some reserved code point of other field (s) in the PBCH content can be combined with 8 bits so that the RMSI CORESET configuration obtains a greater indication range. For example, if an extra bit can be combined, the indication range can be increased to 511 or 512 (depending on which code point indicates no cell definition SS / PBCH block in the band). For another example, if a maximum of 4 other reserved code points can be combined, the indication range can be increased to 1023 or 1024 (depending on which code point indicates that there is no cell definition SS / PBCH block in the band), which may be more sufficient to indicate the scan index within a band for NR.
[00115] [00115] In one example, another field in the code point contained or reserved in the PBCH can be used to indicate the band number, so that if the current synchronization scan where the SS / PBCH block is not associated with ISMS is located in the overlapping bandwidth between
[00116] [00116] In one example, 8 bits of the RMSI CORESET configuration (ie, pdcch-ConfigSIB1) together with the code points reserved in the ssb-SubcarrierOffset in the MIB (note that there are 4 code points reserved in the ssb- SubcarrierOffset, the which can be indicated as r_0, r_1, r_2, r_3) is used as shown in Table 13, where GSCN-first is the first GSCN value for the band currently searched and GSCN-step-size is the step size of the GSCN for the currently searched band (for example, the specific value of GSCN-first and GSCN-step-size for each band can be found in the related wireless specification), and a separate code point is used to indicate that none cell definition SS / PBCH block in the band currently searched (for example, ssb- SubcarrierOffset receives the value of r_0 and pdcch-ConfigSIB1 receives the value of 0).
[00117] [00117] In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb- SubcarrierOffset parameter receives the value of {r_0, r_1, r_2, r_3}, and the UE can assume the ssb mapping - SubcarrierOffset and pdcch-ConfigSIB1 for the synchronization scan GSCN that the UE can search for the cell definition SS / PBCH block within the search band is in accordance with Table 13. Note that the highest number of GSCN for a band of supported NR is 620, which provides the determination of the GSCN range indicated as at most GSCN-first to GSCN-first + 619 * GSCN-step-size in Table 13.
[00118] [00118] If there are new bands defined in the NR, the remaining reserved combination of code points can be used to further increase the indication range. For example, if the largest number of GSCN for a supported NR band is determined to be X, the GSCN range shown in Table 13 can be from GSCN-first to GSCN-first + (X - 1) * GSCN-step-size. Note that the indication capacity in Table 13 can be X up to 1023.
[00119] [00119] Also note that Table 13 can be provided in an equivalent way by a formula. In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb-SubcarrierOffset parameter receives the value of {r_0, r_1, r_2, r_3}, which corresponds to the index-reserved-ssb-SubcarrierOffset receiving the value of {0, 1, 2, 3}, respectively, and the UE can assume the GSCN of the synchronization scan that the UE can search for the cell definition SS / PBCH block within the search band is calculated according to GSCN - cell-defined-SSB = GSCN-first + 256 * index-reserved-ssb- SubcarrierOffset * GSCN-step-size + (pdcch-ConfigSIB1 - 1) * GSCN-step-size, when {index-reserved-ssb-SubcarrierOffset , pdcch-ConfigSIB1} {0, 0}, and the UE does not assume any cell definition SS / PBCH blocks in the band currently searched if {index-reserved-ssb-SubcarrierOffset, pdcch- ConfigSIB1} = {0, 0}, where GSCN-cell-defined-SSB is the GSCN for the next SS / PBCH block defined by cell in the band currently researched, GSCN-first is the first GSCN value of the band currently acting Currently searched, GSCN-step-size is the step size of the GSCN value for the band currently searched, index-reserved-ssb-SubcarrierOffset is the index of the reserved code point in ssb-SubcarrierOffset (receiving the value of {0, 1 , 2, 3}) and pdcch-ConfigSIB1 is receiving the value of {0, 1, ..., 254, 255}.
[00120] [00120] In one embodiment, the GSCN-cell-defined-SSB can be limited to be less than or equal to GSCN-first + 619 * GSCN-step-size at this time and all other code points are reserved for future compatibility. Table 13 Code point GSCN index for SS / PBCH block reserved in ssb- cell definition configuration SubcarrierOffset pdcch-ConfigSIB1 r_0 0 No cell definition SS / PBCH block in the band currently searched r_0 1 GSCN-first r_0 2 GSCN -first + GSCN-step-size ... ... ...
[00121] [00121] In another example, using 8 bits of the RMSI CORESET configuration (pdcch-ConfigSIB1) together with the code points reserved in the ssb-SubcarrierOffset in the MIB (note that there are 4 code points reserved in the ssb- SubcarrierOffset, which can be indicated such as r_0, r_1, r_2, r_3) is shown in Table 14, where GSCN-first is the first GSCN value for the band currently searched and GSCN-step-size is the step size of the GSCN value for the band currently searched (for example, the specific value of GSCN-first and GSCN-step-size for each band can be found in the related wireless communication specification), and no separate code point is used to indicate any cell definition SS / PBCH blocks in the band currently searched since the code point corresponding to the GSCN of the currently located SS / PBCH block is used to indicate the cell definition SS / PBCH block in the currently searched band.
[00122] [00122] In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb- SubcarrierOffset parameter receives the value of {r_0, r_1, r_2, r_3}, and the UE can assume the ssb mapping - SubcarrierOffset and pdcch-ConfigSIB1 for the synchronization scan GSCN that the UE can search for the cell definition SS / PBCH block within the search band is in accordance with Table 14.
[00123] [00123] The UE does not assume any cell definition SS / PBCH block in the band currently researched, if the GSCN for the cell definition SS / PBCH block determined by Table 14 is equal to the GSCN of the current SS / PBCH block. Note that the largest number of GSCN for a supported NR band is 620, which provides the determination of the GSCN range indicated as at most GSCN-first to GSCN-first + 619 * GSCN-step-size in Table 14.
[00124] [00124] If there are new bands defined in the NR, the remaining reserved combination of code points can be used to further increase the indication range. For example, if the largest number of GSCN for a supported NR band is determined to be X, the GSCN range indicated in Table 14 can be from GSCN-first to GSCN-first + (X - 1) * GSCN-step-size . Note that the indication capacity of Table 14 can be X up to 1024. Also note that Table 14 can be provided in an equivalent way by a formula.
[00125] [00125] In the initial selection of cells, a UE can assume that no associated ISMS presents if the upper layer ssb- SubcarrierOffset parameter receives the value of {r_0, r_1, r_2, r_3}, which corresponds to index-reserved-ssb- SubcarrierOffset receiving the value of {0, 1, 2, 3}, respectively, and the UE can assume the GSCN of the synchronization scan that the UE can search for the cell definition SS / PBCH block within the search band is calculated from according to GSCN-cell-defined-SSB = GSCN-first + 256 * index-reserved-ssb-SubcarrierOffset * GSCN-step-size + pdcch-ConfigSIB1 * GSCN-step-size, and the UE does not assume any SS / PBCH blocks definition cell in the band currently researched if GSCN-cell-defined-SSB is equal to the GSCN of the current SS / PBCH block, where GSCN-cell-defined-SSB is the GSCN for the next SS / PBCH block defined by cell within the band currently researched, GSCN-first is the first GSCN value of the band currently researched, GSCN-step-size is the step size of the G value SCN of the band currently searched, index- reserved-ssb-SubcarrierOffset is the index of the reserved code point in ssb-SubcarrierOffset (receiving the value of {0,1,2,3}) and pdcch-ConfigSIB1 is receiving the value of { 0.1, ..., 254.255}. In one embodiment, the GSCN-cell-defined-SSB can be limited to be less than or equal to GSCN-first + 619 * GSCN-step-size at this time and all other code points are reserved for future compatibility.
[00126] [00126] In one embodiment, the field in the PBCH payload is used to indicate the bitmap (bitmap) of the frequency or carrier location bands where the SS / PBCH block (s) associated with an ISMS can be located. After decoding the field in the PBCH payload, the UE can find all frequency location bands in which the SS / PBCH blocks associated with an RMSI can be located. The UE can choose one of the indicated location ranges (for example, indicated as "1" in the bitmap for that frequency range) and blindly search for all synchronization scans within the indicated range.
[00127] [00127] For example, assuming the lowest carrier frequency as F_1 and the highest carrier frequency as F_2. The entire band is divided into N frequency location bands possibly containing the synchronization scans [F_1, F_1 + I_F), [F_1 + I_F, F_1 + 2 * I_F), ..., [F_1 + (N-1) * I_F, F_2], where the range of each range is I_F = (F_2-F_1) / (N-1) and each of the 2 ^ N code points represents a bitmap indicating which of the N ranges containing SS blocks / PBCH with ISMS. Table 15 shows an example of N = 8. Table 16 shows an example of N = 4. Table 15 Code point index Bitmap indicating the frequency location bands that contain synchronization scan (s) 1 00000000 2 00000001 ... ...
[00128] [00128] In another example, assuming the lowest carrier frequency as F_1, the highest carrier frequency as F_2, and the current location (in a synchronization scan) that the UE detects an SS / PBCH block without RMSI as F_S . The remainder of the search band is divided into N frequency location bands, possibly containing the synchronization scans [F_c, F_c + I_F), [F_c + I_F, F_c + 2 * I_F), ..., [F_c + (N-1) * I_F, F_2], where the range of each range is I_F = (F_2-F_c) / (N-1) if the search order is assumed to be low to high in the frequency domain (I_F = (F_c-F_1) / (N-1) and the tracks are
[00129] [00129] In one mode, when multiple SS / PBCH blocks are supported over a broadband, there may be SS / PBCH blocks not located in a synchronization scan. For those SS / PBCH blocks, which may or may not be associated with an RMSI, and whether or not there is an associated RMSI is indicated by a code point in the PRB grid offset indication. If a UE successfully detects the SS / PBCH block in a synchronization scan, and detects that there is no ISMS associated with the SS / PBCH block, the UE can use the 8 bits, which are originally used for RMSI configurations, to indicate the exact location of the next or other SS / PBCH blocks in the synchronization scans, so that the UE can skip some of the synchronization scan locations to search blindly. The entire indication method in Component I can be reused here, if the indicated SS / PBCH (s) are in the synchronization scans.
[00130] [00130] In another mode, when multiple SS / PBCH blocks are supported on a broadband, there may be SS / PBCH blocks not located in a synchronization scan. For those SS / PBCH blocks, which may or may not be associated with an RMSI, and whether or not there is an associated RMSI is indicated by a code point in the PRB grid offset indication. If a UE successfully detects the SS / PBCH block that is not in a synchronization scan and still detects that there is no RMSI associated with the SS / PBCH block, the UE can use the 8 bits, originally used for RMSI configurations, to indicate the exact location of nearby or other SS / PBCH blocks, which may or may not be in the synchronization scans and may or may not have the associated ISMS.
[00131] [00131] In one example, the 8 bits are used to indicate the exact location of another SS / PBCH block, which can be with or without associated RMSI, where each of the 256 code points represents an exact location compared to the current SS / PBCH block without an ISMS. After decoding these 8 bits of the MIB, the UE can directly find the frequency location of another indicated SS / PBCH block. The location relative to the current synchronization scan with a detected SS / PBCH block is measured by the number of PRBs in terms of SS numerology for that band, where the number is always non-negative, which means that the relative location is always defined along the initial cell search order within the band. The code point that defines the relative location "0" of the next SS / PBCH block is essential, as the code point can indicate that within the indication capacity (for example, for a bandwidth of 255 PRBs) using the 8 bits, there is no SS / PBCH synchronization with associated RMSI, and the UE can skip all 255 possible PRBs to search for an SS / PBCH block.
[00132] [00132] In yet another modality, when multiple SS / PBCH blocks are supported in a broadband, there may be SS / PBCH blocks not located in a synchronization scan. For SS / PBCH blocks, which may or may not be associated with an RMSI, and whether or not there is an associated RMSI, it is indicated by a code point in the PRB grid offset indication (ie, a reserved code point in ssb-SubcarrierOffset, for example, r_0). The 8 bits of pdcch-ConfigSIB1 can be reserved for other purposes (for example, configuration of measurement parameters).
[00133] [00133] At least some or all of the following fields are provided to be within the content of a compact DCI format designed exclusively for common control channels, which may include at least one of the remaining minimum system information transmission (ISMS), broadcast information from another system (OSI), pagination, and random access response (RAR) in the 4-step RACH or 2-step RACH.
[00134] [00134] In general, two types of PDSCH resource allocation are defined, in which type 0 uses bitmap to indicate resource allocation with a configurable granularity of frequency resources determined by the size of the BWP (for example, an RBG usually consists of multiple VRBs), and type 1 uses the resource indication value (RIV) to indicate the initial VRB and the length of the contiguous VRBs in the frequency domain with the granularity of 1 VRB.
[00135] [00135] In one embodiment, for the common control channels provided in this disclosure, only a single type of resource allocation scheme is supported in the compact DCI format, and no header bits are essentially necessary to indicate the type of allocation of resources resources (or maintaining the header bit (“hear bit”)
[00136] [00136] In one example, as for common control channels, the message can be received by all UEs in the cell, it is beneficial to try to maximize the use of resources configured with the granularity of X VRBs. Therefore, only the type 1 resource allocation scheme is supported in the compact DCI format. In general, the bit width of the type 1 resource allocation used for the definition of RIV may be related to the size of the BWP, however, for the common control channels provided in this disclosure, the definition of RIV can be optimized, as the size of the BWP for PDSCH is not as flexible as the regular PDSCH data.
[00137] [00137] In one example, the size of the BWP to define the RIV is fixed for all common control channels, for example, 96 (which is the largest number of RBs for the CORESET BW configured in the MIB). Then, the bit width of the field is common to all common control channels. The RIV can be defined according to RIV = 96 * (L_VRB-1) + S_VRB, where L_VRB is the length of the VRBs and S_VRB is the initial VRB index.
[00138] [00138] FIGURE 10 illustrates an example of an SS / PBCH block multiplexed with CORESET of RMSI 1000 according to the modalities of the present disclosure. The RMSI 1000 multiplexed SS / PBCH block modality illustrated in FIGURE 10 is for illustration only. FIGURE 10 does not limit the scope of this disclosure to any specific implementation.
[00139] [00139] Note that a special sub-example of the aforementioned example is L_VRB = CORESET_BW and S_VRB = 0, which means that PDSCH BW is the same as CORESET_BW, and can be applied to some of the multiplexing patterns (for example, at least for Pattern 2 and / or Pattern 3, as in FIGURE 10, and / or in some cases of Pattern 1, where PDSCH coverage is limited as with small BW and / or small number of OFDM symbols). In the sub-example, no bits are required and the RIV value (or equivalently L_VRB and S_VRB) can be hard coded in the specification.
[00140] [00140] In another example, the size of the BWP to define the RIV is the same as the actual CORESET BW configured in the MIB, and may be different for different common control channels. The RIV can be defined according to RIV = CORESET_BW * (L_VRB-1) + S_VRB, where L_VRB is the length of the VRBs, S_VRB is the initial VRB index, and CORESET_BW is the BES of the CORESET configured in the MIB.
[00141] [00141] Note that a special sub-example of this example is L_VRB = CORESET_BW and S_VRB = 0, which means that PDSCH BW is the same as CORESET_BW and can be applied to some of the multiplexing patterns (for example, at least for the Pattern 2 and / or Pattern 3 as in FIGURE 10, and / or in some cases of Pattern 1, where the coverage of the PDSCH is limited as with small BW and / or small number of OFDM symbols). In this sub-example, no bits are required and the RIV value (or equivalently L_VRB and S_VRB) can be hard coded in the specification.
[00142] [00142] In one example (can be applied to all of the above examples), the initial VRB and the length of the contiguous VRBs can be configured based on the # of CCEs, for example, to make the coverage of the PDCCH and PDSCH compatible.
[00143] [00143] In the aforementioned modalities / examples in the type 1 resource allocation scheme, X is the number of VRBs as granularity for resource allocation. Note that the value of X determines the number of bits to express the resource field in the frequency domain. For example, the number of bits can be determined according to log2 [(N_RB ^ BWP / X) * (N_RB ^ BWP / X + 1) / 2], where N_RB ^ BWP is the number of RBs in the given BWP, and for RMSI, N_RB ^ BWP can be the same as CORESET BW in terms of RBs.
[00144] [00144] In one example, X is predefined in the specification, and receives a common value for cases where the type 1 resource allocation scheme is used. For example, X = 1, which corresponds to the most flexible resource allocation case, but may require more bits to express this field. For other instances, X = 2 or 4 or 6, which corresponds to cases of less flexible resource allocation compared to X = 1, but may require fewer bits. For another instance, X is equal to the interleaver granularity.
[00145] [00145] In another example, X is predefined in the specification, and the specific value is defined based on CORESET BW. In this example, there can be multiple values for X, depending on the CORESET BW. The purpose of this multiple granularity for X is to try to align the number of bits to express the resource field in the frequency domain when the total BW is different, for example, CORESET BW in RB / X is a constant, at least for some of the values of CORESET BW. Some specific instances for this example are shown in TABLES 11 to 13. Table 19
[00146] [00146] In yet another example, X is configurable by RRC, and a default value is assumed by the UE on initial access. For example, the pattern X = 1, which corresponds to the most flexible resource allocation case, but may require more bits to express this field, for example, for CORESET BW as 96 RBs, the number of bits required is 13. For other instances, the pattern X = 2 or 4 or 6, which corresponds to cases of less flexible resource allocation compared to X = 1, but may require fewer bits. For another instance, the default X is equal to the interleaver granularity.
[00147] [00147] In another embodiment, for the common control channels provided in this disclosure, both types of resource allocation scheme are supported in the compact DCI format to provide total flexibility for the allocation of PDSCH resources in the frequency domain, and the bitmap definition in type 0 and the definition of RIV in type 1 can refer to the definition for general cases, or using one described in the above modality, where only type 1 resource allocation is supported.
[00148] [00148] In general, the block-interleaved VRB-to-PRB mapping is supported for type 1 resource allocation to obtain frequency diversity gain, and the block-interleaved VRB-to-PRB mapping indication interleaved without block a bit can be carried in DCI format.
[00149] [00149] In one embodiment, for the common control channels provided in the present disclosure, if only the type 1 resource allocation scheme is supported, only the block-interleaved VRB-to-PRB mapping is supported to obtain the gain frequency diversity, and no indication is required in the compact DCI format. In this case, since only the initial active BWP is used to transmit the common control channels, the block-interleaved VRB-to-PRB mapping can be performed across the entire initial active BWP, which is much simpler than a general case where multiple BWPs can exist and overlap. In this modality, the VRB-to-PRB mapping field can be hard-coded in the specification as block-interleaved VRB-to-PRB mapping, and the block size for interleaving can also be hard-coded in the specification (for example, the granularity for resource allocation).
[00150] [00150] In another modality, for the common control channels provided in this disclosure, VRB-to-PRB mapping interleaved in block and interleaved without block are supported, and a bit in the compact DCI format is used to indicate the pattern of VRB-to-PRB mapping (for example, interleaved block or interleaved without block).
[00151] [00151] In general, PDSCH resources in the time domain are characterized by the difference in time at the slot level between the slot containing the corresponding CORESET and the slot containing the PDSCH (for example, indicated as T_slot), together with the initial OFDM symbol in the slot (for example, indicated as S_sym) and length of the OFDM symbols for PDSCH (for example, denoted as L_sym).
[00152] [00152] In one embodiment, for the common control channels provided in this disclosure, PDSCH resources in the time domain can be defined by multiplexing pattern of the SS / PBCH and CORESET / PDSCH block. Note that, as shown in FIGURE 10, three SS / PBCH and CORESET / PDSCH block multiplexing patterns are supported in NR.
[00153] [00153] In one example, Pattern 1 refers to the multiplexing pattern in which the SS / PBCH block and RMSI CORESET occur in different time instances, and the SS / PBCH TX BW block and the initial active DL BWP that contains RMSI CORESET overlay. Note that the time difference between the SS / PBCH block and CORESET / PDSCH can be 0 or greater than one slot.
[00154] [00154] In another example, Pattern 2 refers to the multiplexing pattern in which the SS / PBCH block and RMSI CORESET occur in different time instances, and the SS / PBCH TX BW block and the initial active DL BWP containing RMSI CORESET do not overlap.
[00155] [00155] In yet another example, Pattern 3 refers to the multiplexing pattern in which the SS / PBCH block and RMSI CORESET occur in the same time instance, and the SS / PBCH TX BW block and the initial active DL BWP containing RMSI CORESET do not overlap.
[00156] [00156] In an example, if the multiplexing pattern of the SS / PBCH and CORESET / PDSCH block is set to Pattern 1, which is indicated in the NR-PBCH MIB within the SS / PBCH block, the T_slot can be a number configurable integer with multiple values, and S_sym and L_sym can be encoded together in a RIV. For example, the T_slot slot level difference can be set from 0, 2 * u, 5 * u, 7 * u to <6 GHz and from 0, 2.5 * u, 5 * u, 7.5 * u for> 6 GHz, where u = SS_SCS / 15 kHz. In another instance, S_sym and L_sym can be combined by a RIV coded according to whether L_sym -1 <7, then RIV = 14 * (L_sym -1) + S_sym; otherwise, RIV = 14 * (14-L_sym + 1) + (14-1-S_sym).
[00157] [00157] In one instance, PDSCH resources in the time domain (for example, L_sym, S_sym and T_slot) for Pattern 1 can be determined based on the value M in the Parameters table for PDCCH monitoring occasions, where M is refers to the time difference (measured in slot) between the slots containing CORESET corresponding to the SS / PBCH block with indexes i and i + 1.
[00158] [00158] In one example, T_slot> 0 if M = 2, which means that PDSCH slot cross scaling can be supported if the slot difference between CORESETs is 2 slots.
[00159] [00159] In an example, T_slot = 0 if M = 1/2 and M = 1, which means that scaling the same slot of the PDSCH can be supported if the slot difference between CORESETs is 1/2 and 1 slot.
[00160] [00160] In this example, PDSCH resources in the time domain (for example, L_sym, S_sym and T_slot) for Pattern 1 can be determined based on the configuration of the RMSI in the MIB, that is, RMSI-PDCCH-Config. If a 4-bit table containing a maximum of 16 settings is defined for resources in the PDSCH time domain for the general case, at least one setting in the table can be used for each RMSI setting (that is, each RMSI- PDCCH- Config)
[00161] [00161] In a specific example, only one setting in the table is used for each ISDN setting; the association can then be encoded in the specification and no bits are required for this field. In another specific example, at most the Y settings in the table are used for each RMSI setting, so most log2 (Y) bits are required for this field, for example, Y = 4 for a comprehensive example on complexity and flexibility.
[00162] [00162] In another example, the aforementioned modalities / example can be combined or independent with this example and the PDCCH encryption sequence within CORESET can be based on the SS / PBCH block index, so that the UE can detect the index of SS / PBCH blocks within the duration of the monitoring window and save the transmission of some of the SS / PBCH blocks.
[00163] [00163] In another example, if the multiplexing pattern of the SS / PBCH and CORESET / PDSCH block is set to Pattern 2, indicated in the NR-PBCH MIB in the SS / PBCH block, the T_slot can be hard coded as 0 (or none in this field in DCI format for Standard 2) and S_sym and L_sym can be determined by symbols in the slot mapped to SS / PBCH blocks (for example, determined from the SS block index I_SSB and the SS / block subcarrier spacing) SCCH_SS PBCH). Note that in one embodiment, S_sym and L_sym can still be encoded together by a RIV using the same method as Standard 1, or S_sym and L_sym can be hard coded in the specification and no fields for PDSCH resources in the time domain in DCI format are required.
[00164] [00164] In one instance, S_sym can be the symbol that is mapped to the first symbol in the corresponding SS / PBCH block (ie the symbol mapped to NR-PSS) and L_sym can be hard coded as 4. Table 22 shows a list of examples for this instance. Table 22 SCS_SS T_slot S_sym L_sym RIV (if coded together) 15 kHz 0 2 if mod (I_SSB, 2) = 0; 4 44 if mod (I_SSB, 2) = 0; 8 if mod (I_SSB, 2) = 1 50 if mod (I_SSB, 2) = 1 Mapeame 0 4 if mod (I_SSB, 4) = 0; 4 46 if mod (I_SSB, 4) = 0; 8 if mod (I_SSB, 4) = 1; 50 if mod (I_SSB, 4) = 1; 30 kHz 2 if mod (I_SSB, 4) = 2; 44 if mod (I_SSB, 4) = 2; 1 6 if mod (I_SSB, 4) = 3 48 if mod (I_SSB, 4) = 3 Mapeame 0 2 if mod (I_SSB, 2) = 0; 4 44 if mod (I_SSB, 2) = 0; n of 8 if mod (I_SSB, 2) = 1 50 if mod (I_SSB, 2) = 1
[00165] [00165] In another instance, S_sym can be the symbol that is mapped to the first symbol of the corresponding SS / PBCH block (that is, the symbol mapped to NR-PSS, and you can refer to Table 22 for the particular values of T_slot for each SCS_SS), and L_sym can be configured (for example, configurable from 1, 2, 3 and 4).
[00166] [00166] In yet another example, if the multiplexing pattern of the SS / PBCH and CORESET / PDSCH block is set to Pattern 3, which is indicated in the NR-PBCH MIB in the SS / PBCH block, the T_slot can be rigidly encoded as 0 (or no fields in DCI format for Standard 3), and S_sym and L_sym can be determined by symbols within the slot mapped to SS / PBCH blocks (for example, determined from the SS I_SSB block index and the spacing of sub-carrier of the SS / PBCH block SCS_SS).
[00167] [00167] In one instance, S_sym can be the symbol that is mapped to the third symbol of the corresponding SS / PBCH block (ie, the symbol mapped to NR-SSS and NR-PBCH) and L_sym can be hard coded as 2. Table 23 shows a list of examples for this instance. Table 23 SCS_SS T_slot S_sym L_sym RIV (if coded together) 15 kHz 0 4 if mod (I_SSB, 2) = 0; 2 46 if mod (I_SSB, 2) = 0; 10 if mod (I_SSB, 2) = 1 52 if mod (I_SSB, 2) = 1 Mapeamen 0 6 if mod (I_SSB, 4) = 0; 2 48 if mod (I_SSB, 4) = 0; to 30 if mod (I_SSB, 4) = 52 if mod (I_SSB, 4) = 1; kHz 11; 46 if mod (I_SSB, 4) = 2; 4 if mod (I_SSB, 4) = 2; 50 if mod (I_SSB, 4) = 3 8 if mod (I_SSB, 4) = 3 Mapeamen 0 4 if mod (I_SSB, 2) = 0; 2 46 if mod (I_SSB, 2) = 0; to 30 10 if mod (I_SSB, 2) = 1 52 if mod (I_SSB, 2) = 1 kHz 2 120 kHz 0 6 if mod (I_SSB, 4) = 0; 2 48 if mod (I_SSB, 4) = 0; 10 if mod (I_SSB, 4) = 52 if mod (I_SSB, 4) = 1; 1; 46 if mod (I_SSB, 4) = 2; 4 if mod (I_SSB, 4) = 2; 50 if mod (I_SSB, 4) = 3 8 if mod (I_SSB, 4) = 3
[00168] [00168] In another modality, for the common control channels provided in this disclosure, PDSCH resources in the time domain can be encoded together with PDSCH resources in the frequency domain, and defined by SS / PBCH block multiplexing pattern and CORESET / PDSCH (using the same or different bit width for each multiplexing pattern). Note that, as shown in FIGURE 10, three SS / PBCH and CORESET / PDSCH block multiplexing patterns are supported in NR.
[00169] [00169] In an example, if the SS / PBCH and CORESET / PDSCH block multiplexing pattern is set to Pattern 1, the resources in the time domain and the frequency domain can be coded together, where the total number of ERs it is configurable. In one example, the total number of ERs is compatible with the number of CCEs in CORESET from the perspective of similar coverage.
[00170] [00170] In another example, if the SS / PBCH and CORESET / PDSCH block multiplexing pattern is set to Pattern 2, the resources in the time domain and in the frequency domain can be encoded together, where both resources in the domain time and frequency domain are hard coded.
[00171] [00171] In another example, if the SS / PBCH and CORESET / PDSCH block multiplexing pattern is set to Pattern 3, the resources in the time domain and in the frequency domain can be encoded together, where both resources in the domain time and frequency domain are hard coded.
[00172] [00172] In general, the PDSCH modulation and coding scheme is captured by the MCS table. In one embodiment, for the common control channels provided in this disclosure, the PDSCH modulation and coding scheme can be captured by a compact version of the MCS table, where only low-order modulation schemes are supported in the compact DCI format, from so that the bit width of this field in the compact DCI format can be less than that of other DCI formats.
[00173] [00173] In one mode, within all the common control channels provided in this disclosure, some channels such as OSI and RMSI broadcast encode messages in multiple blocks and mapped to different transmissions, so that the redundancy version is necessary to mark the different coded blocks. Therefore, only for these channels, the compact DCI format can have the redundancy version field with different values (for example, 4 values indicated by 2 bits or 8 values indicated by 3 bits), and, for the other channels, the format Compact DCI can leave the corresponding field as a default value (for example, 0).
[00174] [00174] In another modality, within all the common control channels provided in this disclosure, some channels such as OSI and RMSI broadcast encode messages in multiple blocks and mapped to different transmissions, so that the redundancy version is necessary to mark the different coded blocks. The redundancy version can be determined based on the SFN value (ie the time within the TTI) and known to the UE so that no bits for the redundancy version field are required for the common control channels provided in the present disclosure.
[00175] [00175] In general, the command TPC (Transmission Power Control) can be transmitted as part of the DCI format with common search space. In one embodiment, for the common control channels provided in this disclosure, the compact DCI format may have a field for the TPC Command for PUCCH (for example, with 2 bits). In another embodiment, for the common control channels provided in this disclosure, the field for the compact DCI format is not required before the RRC connection.
[00176] [00176] The header field for the compact DCI format is necessary only when the compact DCI format for common control channels has the same DCI size as another DCI format (for example, some contingency DCI format or other compact DCI format for RACH msg4), in which case the header field is used to distinguish different DCI formats. If there is no DCI format with the same DCI size as the compact DCI format for common control channels, no header fields are essentially necessary.
[00177] [00177] In general, this flag is used to indicate whether reserved resources, both in the frequency domain and in the time domain, are excluded from the rectangular resources allocated to PDSCH, in which the reserved resources can be used for other purposes, for example , for future compatibility or LTE-NR coexistence. In a modality, for the same purpose, these signal (s) are still present for the compact DCI format designed for common control channels. In another modality, this field does not appear before the RRC connection, and is not necessary for the common control channels provided in this disclosure.
[00178] [00178] At least part or all of the following fields are not included in the content of a compact DCI format designed exclusively for common control channels, which can include at least one of the RMSI, OSI, pagination and RAR transmission.
[00179] [00179] The common control channels provided in this disclosure are primarily for initial access purposes, therefore, the carrier and BWP to transmit the common control channels provided in this disclosure do not need to be configured or assigned. In one embodiment, the compact DCI format for the common control channels provided in this disclosure does not contain the carrier indicator or BWP indicator fields.
[00180] [00180] In one embodiment, the packet size for PDSCH for the common control channels provided in this disclosure is fixed (for example, 6 PRBs), and the compact DCI format for the common control channels provided in this disclosure does not contain the packet size indicator field.
[00181] [00181] The common control channels provided in this disclosure may not have new data transmission, therefore, the new data indicator is not applicable. In one embodiment, the compact DCI format for the common control channels provided in this disclosure does not contain the new data indicator field.
[00182] [00182] The common control channels provided in this disclosure may have only a single code word and the parameters related to the second code word may not be applicable to the common control channels. In one embodiment, the compact DCI format for the common control channels provided in this disclosure does not contain the parameter fields for the second code word, including modulation and coding scheme, new data indicator, and redundancy version.
[00183] [00183] The common control channels provided in this disclosure may not have any HARQ process, and the parameters related to HARQ may not be applicable to the common control channels. In one embodiment, the compact DCI format for the common control channels provided in this disclosure does not contain the parameter fields for the HARQ process, including the HARQ process number, CBGFI, CBGTI, ACK / NACK resource index, time indicator HARQ and downlink assignment index.
[00184] [00184] Note that in a modality, if the compact DCI format is also applicable to the RACH msg4, the parameters related to the HARQ process can be provided as fields in the compact DCI format.
[00185] [00185] The common control channels provided in this disclosure may not have multiple configurations for antenna ports and may only support single layer transmission, so that the configuration for antenna port (s) can be fixed for PDSCH of the transmission channels. common control. In one embodiment, the compact DCI format for the common control channels provided in this disclosure does not contain the field for the antenna ports.
[00186] [00186] In general, the Transmission Configuration Indication (TCI) is used to provide beam indication to indicate QCL assumption between DL RS antenna port (s) and channel DMRS antenna port (s) DL data at least spatial QCL parameter wrt For the common control channels provided in this disclosure, all common control channels are QCLed with the corresponding SS / PBCH block, so that no TCI is required for the common control channels. In one embodiment, the compact DCI format for the common control channels provided in this disclosure does not contain the field for TCI.
[00187] [00187] An example of the compact DCI format design for common control channels is shown in Table 24, where the total size of the DCI is about 20 to 30 bits, much smaller than other DCI formats (for example, by least 40 to 50 bits). Table 24 #Bits field PDSCH resources in the frequency domain 13 PDSCH resources in the time domain ≤4 VRB-to-PRB mapping type 1
[00188] [00188] In another example of the compact DCI format design for common control channels, it is shown in Table 25, where the total size of the DCI is based on the SS / PBCH block and the CORESET multiplexing pattern, which is about 15 bits for Pattern 1 and less than 5 bits for Pattern 2 and Pattern 3. Table 25 #Bits field for #Bits pattern for multiplexing pattern 1 multiplexing 2 and 3 PDSCH resources in the 13 ≤13 frequency domain PDSCH resources in the ≤2 domain 0 time Modulation Scheme and <5 <5 Coding Table 25 Compact DCI format design
[00189] [00189] The DMRS sequence of the PDCCH is constructed by the Gold sequence modulated with QPSK which is the XOR of two M sequences of length L, where one of the M sequences sA (n) is generated with the generator gA (x) and the initial condition cA, and the other sequence M sB (n) is generated with generator gB (x) and initial condition cB. There is a possible shift of Nc output shift (for example, Nc = 1600 as in LTE), so that the Gold sequence modulated by QPSK s (n) = (1- 2 * ((sA (2n + Nc) + sB (2n + Nc)) mod 2)) / v2 + j * (1-2 * ((sA (2n + Nc + 1) + sB (2n + Nc + 1)) mod 2)) / v2 es (n ) are truncated to the desired length of the desired DMRS N_DMRS sequence. The length L of the Gold-sequence is the same as LTE-CRS (for example, 2 ^ 31-1), and one of the sequence M sA (n) is given by gA (x) = x³¹ + x³ + 1 with initial condition fixed cA (for example, cA = 1), and the other sequence M sB (n) is given by gB (x) = x³¹ + x³ + x² + x + 1 with the initial condition cB. The initial condition cB carries the ID (or cell ID or C-RNTI) and the time-related index, so that the DMRS sequence varies over time.
[00190] [00190] In one embodiment, the time-related index contains slot index and symbol index, and the initial condition is a product form of the ID and time-related index.
[00191] [00191] In one example, cB = mod (c_1 * (N_ID + 1) * (14 * N_slot + N_symbol + 1) + c_2 * (14 * N_slot + N_sy symbol + 1) + c_3 * (N_ID + 1), 2 ^ 31) where c_1, c_2 and c_3 are predefined integers. Note that in this example, c_1> 2 ^ 12, so mod 2 ^ 31 is required.
[00192] [00192] In another example, cB = mod (c_1 * (2 * N_ID + 1) * (14 * N_slot + N_symbol + 1) + c_2 * (14 * N_slot + N_ symbol + 1) + c_3 * (2 * N_ID +1), 2 ^ 31) where c_1, c_2 and c_3 are predefined integers. Note that, in this example, c_1> 2 ^ 11, so mod 2 ^ 31 is required.
[00193] [00193] In another example, cB = c_1 * (N_ID + 1) * (14 * N_slot + N_symbol + 1) + c_2 * (14 * N_slot + N_symbol +1) + c_3 * (N_ID + 1) where c_1, c_2 and c_3 are predefined integers. Note that in this example, c_1≤2 ^ 12. In one instance, c_1 = 2, c_2 = 2 ^ 12 and c_3 = 0, that is, cB = 2 * (N_ID + 1) * (14 * N_slot + N_symbol + 1 ) + 2 ^ 12 * (14 * N_slot + N_symbol + 1).
[00194] [00194] In another example, cB = c_1 * (2 * N_ID + 1) * (14 * N_slot + N_symbol + 1) + c_2 * (14 * N_slot + N_symb ol + 1) + c_3 * (2 * N_ID + 1 ) where c_1, c_2 and c_3 are predefined integers. Note that in this example, c_1≤2 ^
[00195] [00195] FIGURE 11 illustrates a flow chart of a method 1100 for a UE according to the modalities of the present disclosure. The method 1100 method illustrated in FIGURE 11 is for illustration only. FIGURE 11 does not limit the scope of the present disclosure to any specific implementation.
[00196] [00196] As illustrated in FIGURE 11, method 1100 starts at the beginning. In step 1102, the UE (for example, 111-116, as illustrated in FIGURE 1) receives, from a base station (BS), a physical transmission channel block (SS / PBCH) synchronization signal including the PBCH using a first frequency location (GSCN-Current) on downlink channels, the GSCN-Current being based on a set of predefined synchronization scans, determined by a global synchronization channel number (GSCN).
[00197] [00197] In one embodiment, in step 1102, the SS / PBCH block that is associated with the PDCCH, including the scheduling information for the RMSI in the given GSCN-Current, is indicated by at least one of a first carrier frequency range , a ssb -SubcarrierOffset field in the PBCH content based on a value of {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15} and a field in the PBCH content with a value of 0, for the first carrier frequency range, the ssb-SubcarrierOffset field in the PBCH content based on a value of {0, 1, 2, 3, 4, 5, 6, 7} and the PBCH content field with a value of 1 or, for a second carrier frequency range, the ssb-SubcarrierOffset field in the PBCH content based on a value of {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11}.
[00198] [00198] In one mode, in step 1102, the SS / PBCH block that is not associated with the PDCCH, including the scheduling information for the RMSI in the determined GSCN-Current, is indicated by at least one of, for a first range of frequency, an ssb-SubcarrierOffset field in the PBCH content based on a value of {8, 9, 10, 11, 12, 13, 14, 15} and a field in the PBCH content with a value of 1 or for a second frequency range, the ssb- SubcarrierOffset field in the PBCH content based on a value of {12, 13, 14, 15}.
[00199] [00199] In such a modality, a frequency range in which no other SS / PBCH block configured with the PDCCH, including the scheduling information for ISMS, is transmitted, is indicated by at least one of a first carrier frequency range. , GSCN-Current - pdcch- ConfigSIB1 / 16 to GSCN-Current + pdcch-ConfigSIB1 mod 16 when a ssb-SubcarrierOffset field in the PBCH content with a value of 15 and a field in the PBCH content with a value of 1 or for a second carrier frequency range, GSCN-Current - pdcch-ConfigSIB1 / 16 to GSCN-Current + pdcch-ConfigSIB1 mod 16 when the ssb- SubcarrierOffset field in the PBCH content with a value of 15. In such a mode, the pdcch -ConfigSIB1 comprises a length of 8 bits in the content of the PBCH.
[00200] [00200] In such modality, the frequency range in which no other SS / PBCH blocks configured with the PDCCH, including the scheduling information for the ISDN, is transmitted is provided by GSCN-Current when pdcch-ConfigSIB1 = 0.
[00201] [00201] In such a modality, the second frequency location in which other SS / PBCH blocks configured with the PDCCH, including the scheduling information for the ISMS, are transmitted, is indicated by at least one of the, for a first frequency range of carrier 1, GSCN-Current + 256 * (ssb-SubcarrierOffset-8) + pdcch-ConfigSIB1 + 1 when a ssb-SubcarrierOffset field in the PBCH content based on a value of {8, 9, 10} and a field in the PBCH content with a value of 1, for the first carrier frequency range 1, GSCN-Current - 256 * (ssb-SubcarrierOffset-11) - pdcch-ConfigSIB1-1 when the ssb-SubcarrierOffset field in the PBCH content with based on a value of {11, 12, 13} and the PBCH content field with a value of 1, for a second carrier frequency range, GSCN-Current + pdcch-ConfigSIB1 + 1 when the ssb- SubcarrierOffset in the PBCH content with a value of 12, or for the second carrier frequency range, GSCN-Current - pdcch-ConfigSIB1- 1 qu walk the ssb-SubcarrierOffset field in the PBCH content with a value of 13.
[00202] [00202] In such a modality, pdcch-ConfigSIB1 has a length of 8 bits in the content of the PBCH.
[00203] [00203] In one embodiment, when the SS / PBCH block is configured with a PDCCH including the scheduling information for the RMSI in the given GSCN-Current, the processor is further configured to determine the scheduling information for the RMSI based on a SS / PBCH multiplexing standard and a set of control resources (CORESET) including PDCCH, the scheduling information for ISMS, including at least one resource allocation in the time domain of a physical downlink shared channel (PDSCH) ) for ISMS.
[00204] [00204] In step 1104, the UE decoded a PBCH included in the received SS / PBCH block.
[00205] [00205] In step 1106, the UE identifies the content of the decoded PBCH.
[00206] [00206] In step 1108, the UE determines a configuration for at least one of the SS / PBCH blocks that is associated with a physical downlink control channel (PDCCH), including scheduling information for the minimum remaining system information (RMSI ) in the GSCN-Current or SS / PBCH that is not associated with the PDCCH, including the scheduling information for RMSI in the GSCN-Current.
[00207] [00207] In step 1110, the UE determines, when the SS / PBCH block is not associated with the PDCCH, including the scheduling information for the RMSI in GSCN-Current, the configuration to include at least one frequency range in which no other SS / PBCH block configured with the PDCCH, including the scheduling information for ISMS, is transmitted, the frequency range determined based on the GSCN or a second frequency location in which other SS / PBCH blocks configured with the PDCCH including the information escalation points for ISMS are transmitted, the GSCN-Current determined based on the GSCN.
[00208] [00208] FIGURE 12 illustrates a flow chart of a method 1200 for a BS according to the modalities of the present disclosure. The method 1200 method illustrated in FIGURE
[00209] [00209] As illustrated in FIGURE 12, method 1200 begins at step 1202. BS (for example, 101-103, as illustrated in FIGURE 1). In step 1202, the BS generates a synchronization signal and physical transmission channel block (SS / PBCH).
[00210] [00210] In one modality, in step 1202, the SS / PBCH block that is associated with the PDCCH, including the scheduling information for the RMSI in the determined GSCN-Current, is indicated by at least one among a first carrier frequency range , an ssb-SubcarrierOffset field in the PBCH content based on a value of {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15} and a field in the PBCH content with a value of 0, for the first carrier frequency range, the ssb-SubcarrierOffset field in the PBCH content based on a value of {0, 1, 2, 3, 4, 5, 6, 7} and the PBCH content field with a value of 1 or, for a second carrier frequency range, the ssb-SubcarrierOffset field in the PBCH content based on a value of {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11}.
[00211] [00211] In one modality, in step 1202, the SS / PBCH block that is not associated with the PDCCH, including the scheduling information for the RMSI in the determined GSCN-Current, is indicated by at least one of, for a first range of frequency, an ssb-SubcarrierOffset field in the PBCH content based on a value of {8, 9, 10, 11, 12, 13, 14, 15} and a field in the PBCH content with a value of 1 or for a second frequency range, the ssb- SubcarrierOffset field in the PBCH content based on a value of {12, 13, 14, 15}.
[00212] [00212] In such a modality, a frequency range in which no other SS / PBCH blocks configured with the PDCCH, including the scheduling information for ISMS, is transmitted, is indicated by at least one of, for a first frequency range of carrier, GSCN-Current - pdcch-ConfigSIB1 / 16 to GSCN-Current + pdcch-ConfigSIB1 mod 16 when a ssb-SubcarrierOffset field in the PBCH content with a value of 15 and a field in the PBCH content with a value of 1 or, for a second carrier frequency range, GSCN-Current - pdcch-ConfigSIB1 / 16 to GSCN-Current + pdcch-ConfigSIB1 mod 16 when the ssb- SubcarrierOffset field in the PBCH content with a value of 15.
[00213] [00213] In such a modality, pdcch-ConfigSIB1 comprises a length of 8 bits in the content of the PBCH.
[00214] [00214] In such a modality, the frequency range in which no other SS / PBCH blocks configured with the PDCCH, including the scheduling information for the RMSI, is transmitted is provided by GSCN-Current when pdcch-ConfigSIB1 = 0.
[00215] [00215] In such an embodiment, the second frequency location in which other SS / PBCH blocks configured with the PDCCH, including the scheduling information for the ISMS, are transmitted, is indicated by at least one of, for a first frequency range of carrier 1, GSCN-Current + 256 * (ssb-SubcarrierOffset-8) + pdcch-ConfigSIB1 + 1 when a ssb-SubcarrierOffset field in the PBCH content based on a value of {8, 9, 10} and a field in the PBCH content with a value of 1, for the first carrier frequency range 1, GSCN-Current - 256 * (ssb-SubcarrierOffset-11) - pdcch-ConfigSIB1-1 when the ssb-SubcarrierOffset field in the PBCH content with based on a value of {11, 12, 13} and the PBCH content field with a value of 1, for a second carrier frequency range, GSCN-Current + pdcch-ConfigSIB1 + 1 when the ssb- SubcarrierOffset in the PBCH content with a value of 12, or for the second carrier frequency range, GSCN-Current - pdcch-ConfigSIB1- 1 qu walk the ssb-SubcarrierOffset field in the PBCH content with a value of 13.
[00216] [00216] In such modality, pdcch-ConfigSIB1 has a length of 8 bits in the content of the PBCH, and the SS / PBCH block is configured with a PDCCH including the scheduling information for the RMSI in the determined GSCN-Current, determining the information scheduling for ISMS based on a SS / PBCH block multiplexing standard and a set of control resources (CORESET) including PDCCH, scheduling information for ISMS, including at least one resource allocation in the domain time of a physical downlink shared channel (PDSCH) for ISMS.
[00217] [00217] In step 1204, BS identifies a first frequency location (GSCN-Current) based on a set of predefined synchronization scans that is determined by a global synchronization channel number (GSCN) to transmit the SS / block PBCH.
[00218] [00218] In step 1206, BS determines, based on GSCN-Current, a configuration for at least one of the SS / PBCH blocks that is associated with a physical downlink control channel (PDCCH), including scheduling information for the minimum remaining system information (RMSI) in the GSCN-Current or SS / PBCH block that is not associated with the PDCCH, including the scheduling information for the RMSI in the GSCN-Current.
[00219] [00219] In step 1208, the BS determines, when the SS / PBCH block is not associated with the PDCCH, including the scheduling information for the RMSI in the GSCN-Current, the configuration to include at least one of a frequency range in which no other SS / PBCH blocks configured with the PDCCH, including scheduling information for the ISMS, are transmitted, the frequency range determined based on the GSCN, or a second frequency location in which other SS / PBCH blocks configured with the PDCCH , including scheduling information for ISMS, are transmitted, the GSCN-Current determined based on the GSCN.
[00220] [00220] In step 1210, the BS identifies, based on the determined configuration, the content of a PBCH included in the SS / PBCH block.
[00221] [00221] In step 1212, the BS transmits, to a user equipment (UE), the SS / PBCH block, including the PBCH, using the GSCN-Current on downlink channels.
[00222] [00222] Although the present disclosure has been described with an exemplary modality, several changes and modifications can be suggested to a person skilled in the art. It is intended that the present disclosure includes the changes and modifications that fall within the scope of the attached claims.
[00223] [00223] None of the descriptions in this application should be read as implying that any particular element, step or function is an essential element that should be included in the scope of the statements. The scope of the patented object is defined only by the claims. In addition, none of the claims are intended to invoke 35 USC § 112 (f), unless the exact words "means for" are followed by a participle.

权利要求:
Claims (20)
[1]
1. Method performed by a terminal in a wireless communication system, the method characterized by the fact that it comprises: receiving, from a base station, a first block of synchronization signal (SSB); identify whether a first set of control resources (CORESET) for the system information block (SIB) is present based on the first information included in the first SSB; identifying a frequency position of a second SSB having a second CORESET for SIB based on the first information and second information included in the first SSB, in the event that the first CORESET for SIB is not present; and receive, from the base station, the SIB monitoring a research space in the second CORESET based on the second SSB, in which the first CORESET is identified as being present, in the case where the first information corresponds to a first range of values, in which the first CORESET is identified as not being present, in the case where the first information corresponds to a second range of values.
[2]
2. Method, according to claim 1, characterized by the fact that it is determined that there is no SSB having a CORESET for SIB within a range of global synchronization channel number (GSCN) based on the second information, in the case in that the first information corresponds to a first value within the second range of values.
[3]
3. Method according to claim 2,
characterized by the fact that an beginning of the GSCN range is identified based on the four most significant bits (MSBs) of the second information, and that an end of the GSCN range is identified based on four less significant bits (LSBs) of the second information information.
[4]
4. Method, according to claim 2, characterized by the fact that it is determined that there is no information for the SSB having CORESET for SIB in the first SSB, in the case where the first information corresponds to the first value and the second information corresponds to a second value.
[5]
5. Method, according to claim 1, characterized by the fact that the frequency position of the second SSB is identified based on a GSCN of the first SSB and a displacement of GSCN, the displacement of GSCN being determined based on the second information in the case where the first information corresponds to a third value within the second range of values, and where the first information indicates a subcarrier shift between the first SSB and a resource block grid.
[6]
6. Method performed by a base station in a wireless communication system, the method characterized by the fact that it comprises: transmitting, to a terminal, a first block of synchronization signal (SSB), in which a first set of resources control (CORESET) for the system information block (SIB) is present is identified based on the first information included in the first SSB;
transmit to the terminal a second SSB having a second CORESET for SIB, in which a frequency position of the second SSB is identified based on the first information and the second information included in the first SSB, in the case where the first CORESET for SIB is not present; and transmit, to the terminal, the SIB based on the second SSB, in which the first CORESET is identified as being present, in the case where the first information corresponds to a first range of values, in which the first CORESET is identified as not being present , in the case where the first information corresponds to a second range of values.
[7]
7. Method according to claim 6, characterized by the fact that it is determined that there is no SSB having a CORESET for SIB within a range of global synchronization channel number (GSCN) based on the second information, in the case in that the first information corresponds to a first value within the second range of values.
[8]
8. Method according to claim 7, characterized by the fact that a start of the GSCN range is identified based on the four most significant bits (MSBs) of the second information, and in which an end of the GSCN range is identified with based on four least significant bits (LSBs) of the second information.
[9]
9. Method, according to claim 7, characterized by the fact that it is determined that there is no information for the SSB having CORESET for SIB in the first SSB, in the case where the first information corresponds to the first value and the second information corresponds to a second value.
[10]
10. Method according to claim 6, characterized by the fact that the frequency position of the second SSB is identified based on a GSCN of the first SSB and an offset of GSCN, the offset of GSCN being determined based on the second information in the case where the first information corresponds to a third value within the second range of values, and where the first information indicates a subcarrier shift between the first SSB and a resource block grid.
[11]
11. Terminal in a wireless communication system, the terminal characterized by the fact that it comprises: a transceiver configured to transmit and receive a signal; and a controller coupled to the transceiver and configured to: receive, from a base station, a first block of synchronization signal (SSB), identify whether a first set of control resources (CORESET) for the system information block (SIB) is present based on the first information included in the first SSB, identifying a frequency position of a second SSB having a second CORESET for SIB based on the first information and second information included in the first SSB, in the case where the first CORESET for SIB does not is present, and receive, from the base station, the SIB monitoring a research space in the second CORESET based on the second SSB, in which the first CORESET is identified as being present, in the case where the first information corresponds to a first range of values , in which the first CORESET is identified as not being present, in the case where the first information corresponds to a second range of values.
[12]
12. Terminal, according to claim 11, characterized by the fact that it is determined that there is no SSB having a CORESET for SIB within a range of global synchronization channel number (GSCN) based on the second information, in the case in that the first information corresponds to a first value within the second range of values.
[13]
13. Terminal according to claim 12, characterized by the fact that a start of the GSCN range is identified based on the four most significant bits (MSBs) of the second information, and in which an end of the GSCN range is identified with based on four least significant bits (LSBs) of the second information.
[14]
14. Terminal, according to claim 12, characterized by the fact that it is determined that there is no information for the SSB having the CORESET for SIB in the first SSB, in the case where the first information corresponds to the first value and the second information corresponds to a second value.
[15]
15. Terminal, according to claim 11, characterized by the fact that the frequency position of the second SSB is identified based on a GSCN of the first SSB and an offset of GSCN, the offset of GSCN being determined based on the second information , in the case where the first information corresponds to a third value within the second range of values, and where the first information indicates a subcarrier shift between the first SSB and a resource block grid.
[16]
16. Base station in a wireless communication system, the base station characterized by the fact that it comprises: a transceiver configured to transmit and receive a signal; and a controller coupled to the transceiver and configured to: transmit, to a terminal, a first block of synchronization signal (SSB), in which there is a first set of control resources (CORESET) for the system information block (SIB) is present is identified based on the first information included in the first SSB, transmitting to the terminal a second SSB having a second CORESET for SIB, in which a frequency position of the second SSB is identified based on the first information and the second information included in the first SSB, in the case where the first CORESET for SIB is not present and transmit, to the terminal, the SIB based on the second SSB, in which the first CORESET is identified as being present, in the case where the first information corresponds to a first range of values, where the first CORESET is identified as not being present, in the case where the first information corresponds to a second range of values.
[17]
17. Base station, according to claim 16, characterized by the fact that there is no SSB having a CORESET for SIB within a range of global synchronization channel number (GSCN) based on the second information, in the case where the first information corresponds to a first value within the second range of values.
[18]
18. Base station, according to claim 17, characterized by the fact that a start of the GSCN range is identified based on the four most significant bits (MSBs) of the second information, and in which an end of the GSCN range is identified based on four least significant bits (LSBs) of the second information.
[19]
19. Base station, according to claim 17, characterized by the fact that there is no information for the SSB having the CORESET for SIB in the first SSB, in the case where the first information corresponds to the first value and the second information corresponds to a second value.
[20]
20. Base station according to claim 16, characterized by the fact that the frequency position of the second SSB is identified based on a GSCN from the first SSB and an offset from GSCN, the offset from GSCN being determined based on the second information, in the case where the first information corresponds to a third value within the second range of values, and where the first information indicates a subcarrier shift between the first SSB and a resource block grid.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112020012590A2|2020-11-24|method and apparatus for indicating the frequency location of ss / pbch blocks

---

US20190230706A1|2019-07-25|Listen-before-talk for wideband operations of nr unlicensed spectrum

---

JP6404344B2|2018-10-10|Device-to-device terminal signal transmission / reception method and apparatus in a wireless communication system

---

US11160050B2|2021-10-26|Method and apparatus for supporting large subcarrier spacing for SS/PBCH block

---

US9326122B2|2016-04-26|User equipment and method for packet based device-to-device | discovery in an LTE network

---

JP6162244B2|2017-07-12|Terminal apparatus, base station apparatus, and communication method

---

CN107836093B|2020-11-13|Method and user equipment for receiving downlink signal, and method and base station for transmitting downlink signal

---

JP6163554B2|2017-07-12|Terminal apparatus, base station apparatus, and communication method

---

RU2761513C2|2021-12-09|Base station device, terminal device, communication method and integral circuit

---

US11071000B2|2021-07-20|Method and apparatus for RRM measurement enhancement for NR unlicensed

---

KR20200090835A|2020-07-29|Method and apparatus for initial access block for standalone NR unlicensed spectrum

---

EP3031189A1|2016-06-15|User equipment and method for packet based device-to-device | discovery in an lte network

---

KR20200075782A|2020-06-26|Sequence design of wake-up signal and resynchronization sequence

---

PT2104294E|2012-09-12|Monitoring a control channel in a wireless communication system

---

JPWO2018199240A1|2020-03-12|Terminal device, base station device, and communication method

---

KR20210122812A|2021-10-12|Methods and Apparatus for Determining Effective RACH Opportunities in Unlicensed NRs

---

CN113316951A|2021-08-27|Method and apparatus for performing communication in wireless communication system

---

CN113519137A|2021-10-19|Method and apparatus for multi-beam operation

---

ES2840062T3|2021-07-06|Procedures and support apparatus of multiple services in wireless communication system

---

US20210076341A1|2021-03-11|Method and apparatus for s-ssb transmission

---

KR20210122417A|2021-10-12|Method and apparatus for performing communication in wireless communication system

---

KR20220021457A|2022-02-22|Method and apparatus for synchronization signal/physical broadcast channel | block repetition

---

BR112020011784A2|2020-11-24|reliable low-latency operations on time division duplexing unwired communication systems

---

JP2015070342A|2015-04-13|Base station, terminal, and communication method

---

BR112012012995B1|2021-09-21|METHOD FOR A SOUND REFERENCE SIGNAL SETTING, BASE STATION FOR A SOUND REFERENCE SIGNAL SETTING AND USER EQUIPMENT

同族专利:

---

公开号 | 公开日

---

EP3711390A4|2020-12-16|

---

WO2019125063A9|2020-04-16|

---

US20210344470A1|2021-11-04|

---

RU2020123769A|2022-01-21|

---

RU2020123769A3|2022-01-28|

---

CN111492703A|2020-08-04|

---

US11070333B2|2021-07-20|

---

KR20200091849A|2020-07-31|

---

EP3711390A1|2020-09-23|

---

WO2019125063A1|2019-06-27|

---

US20190200307A1|2019-06-27|

---

JP2021508201A|2021-02-25|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US10178612B2|2016-04-26|2019-01-08|Qualcomm Incorporated|Enhanced machine-type communications cell acquisition using narrow band synchronization channel|

---

US10270573B2|2017-05-16|2019-04-23|Qualcomm Incorporated|Techniques and apparatuses for reusing remaining minimum system information configuration bits to signal a synchronization signal block location|

---

US10856332B2|2017-06-23|2020-12-01|Mediatek Inc.|Method and apparatus for random access channel procedure in wireless communication system|

---

US10727968B2|2017-09-15|2020-07-28|Qualcomm Incorporated|Synchronization signal block and control resource set multiplexing|

---

US10616877B2|2017-11-16|2020-04-07|Huawei Technologies Co., Ltd.|Configuration of the initial active bandwidth part for initial network access|

---

US10791550B2|2017-11-17|2020-09-29|Lg Electronics Inc.|Method of transmitting and receiving downlink channel and apparatus therefor|

---

US10993248B2|2017-11-17|2021-04-27|Qualcomm Incorporated|Designs for remaining minimum system information control resource set and other system information coreset|

---

US11259237B2|2018-01-15|2022-02-22|Qualcomm Incorporated|System and method for locating a downlink data channel|

---

US20190327767A1|2018-04-18|2019-10-24|Qualcomm Incorporated|Search space configurations for random access messaging|JP6663078B2|2017-06-16|2020-03-11|エルジー エレクトロニクス インコーポレイティド|Method for transmitting / receiving downlink channel and apparatus therefor|

---

CN110034888A|2018-01-12|2019-07-19|华为技术有限公司|A kind of wireless communication device and wireless communications method|

---

EP3742841B1|2018-02-14|2022-03-09|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|Indication method, detection method and related device|

---

WO2019184675A1|2018-03-28|2019-10-03|Telefonaktiebolaget Lm Ericsson |Method and apparatus for using indication information of time domain resource allocation|

---

US10912047B2|2018-03-29|2021-02-02|Lg Electronics Inc.|Method and apparatus for transmitting and receiving system information|

---

US11197294B2|2018-08-17|2021-12-07|Qualcomm Incorporated|Synchronization signal block and remaining minimum system information integration in unlicensed systems|

---

US11234219B2|2019-01-11|2022-01-25|Intel Corporation|Discovery reference signal and control resource set multiplexing|

---

US20210007066A1|2019-07-03|2021-01-07|Samsung Electronics Co., Ltd.|Method and apparatus for rmsi reception for low cost ues in nr|

---

CN112398573A|2019-08-14|2021-02-23|华为技术有限公司|Scrambling and descrambling method, network equipment and terminal equipment|

---

US20210067298A1|2019-08-29|2021-03-04|Samsung Electronics Co., Ltd.|Method and apparatus for rmsi reception from a neighboring cell|

---

WO2021088084A1|2019-11-08|2021-05-14|Oppo广东移动通信有限公司|Method for indicating position of synchronisation signal blocks and related device|

---

US20210235419A1|2020-01-22|2021-07-29|Samsung Electronics Co., Ltd.|Method and apparatus for pbch payload in higher frequency ranges|

---

US20210321374A1|2020-04-13|2021-10-14|Qualcomm Incorporated|Alternatively sized downlink control information messages for scheduling remaining minimum system information transmissions|

---

WO2021208977A1|2020-04-14|2021-10-21|华为技术有限公司|Method and apparatus for transmitting synchronization/physical broadcast channel block|

法律状态:
2021-12-07| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762608768P| true| 2017-12-21|2017-12-21|

---

US62/608,768|2017-12-21|

---

US201762609914P| true| 2017-12-22|2017-12-22|

---

US62/609,914|2017-12-22|

---

US201862614718P| true| 2018-01-08|2018-01-08|

---

US62/614,718|2018-01-08|

---

US201862616796P| true| 2018-01-12|2018-01-12|

---

US62/616,796|2018-01-12|

---

US201862625651P| true| 2018-02-02|2018-02-02|

---

US62/625,651|2018-02-02|

---

US201862628475P| true| 2018-02-09|2018-02-09|

---

US62/628,475|2018-02-09|

---

US201862710373P| true| 2018-02-16|2018-02-16|

---

US62/710,373|2018-02-16|

---

US201862635695P| true| 2018-02-27|2018-02-27|

---

US62/635,695|2018-02-27|

---

US201862636271P| true| 2018-02-28|2018-02-28|

---

US62/636,271|2018-02-28|

---

US201862638551P| true| 2018-03-05|2018-03-05|

---

US62/638,551|2018-03-05|

---

US201862758111P| true| 2018-11-09|2018-11-09|

---

US62/758,111|2018-11-09|

---

US16/218,137|US11070333B2|2017-12-21|2018-12-12|Method and apparatus for SS/PBCH block frequency location indication|

---

US16/218,137|2018-12-12|

---

PCT/KR2018/016499|WO2019125063A1|2017-12-21|2018-12-21|Method and apparatus for ss/pbch block frequency location indication|

---